Jump to content


Photo

bug driver mount loop [ET9X00]


  • Please log in to reply
1 reply to this topic

#1 loulou2000

  • Senior Member
  • 37 posts

0
Neutral

Posted 17 February 2012 - 22:11

hello there is a problem on the loop with NLE, its been a momment that I noticed, see the log

podhd 2.1 et9x00
 
et9x00 login: root
 
Password:
 
root@et9x00:~# mkfs.ext4 -b 4096 /hdd/loopext4
 
mke2fs 1.42 (29-Nov-2011)
 
/hdd/loopext4 is not a block special device.
 
Proceed anyway? (y,n) y
 
Filesystem label=
 
OS type: Linux
 
Block size=4096 (log=2)
 
Fragment size=4096 (log=2)
 
Stride=0 blocks, Stripe width=0 blocks
 
16384 inodes, 16384 blocks
 
819 blocks (5.00%) reserved for the super user
 
First data block=0
 
Maximum filesystem blocks=16777216
 
1 block group
 
32768 blocks per group, 32768 fragments per group
 
16384 inodes per group
 
Allocating group tables: done
 
Writing inode tables: done
 
Creating journal (1024 blocks): done
 
Writing superblocks and filesystem accounting information: done
 
root@et9x00:~# mount -t ext4 -o loop /media/hdd/loopext4 /media/net
 
 
mount: mount -t ext4 -o loop /media/hdd/loopext4 /media/net
 
mount: mounting /media/hdd/loopext4 on /media/net failed: Block device required
 
root@et9x00:~#
 
 


Re: bug driver mount loop [ET9X00] #2 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 17 February 2012 - 22:29

We are using busybox mount, which doesn't implement all features of the full-blown mount.

However, the workaround is easy, you have to just call losetup yourself:

root@et9x00:~# losetup /dev/loop0 /hdd/loopext4
root@et9x00:~# mount -t ext4 /dev/loop0 /media/net


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users