Hello linux-il,

First, running this series of actions (as many know) creates and mounts
an ext3 filesystem on my linux machine:

dd if=/dev/zero of=/test/disk-image count=10240
mkfs -t ext3 /test/disk-image
mount -o loop -t ext3  /test/disk-image /loopDir
ls /loopDir
  => gives lost+found

Now I tried the same with ufs filesystem (which is common in *BSD
and solaris os's ; in linux the ufs support is read-only):

First, I had built the ufs module and insmoded it.
Running "cat /proc/filesystems |grep ufs" shows that it exists.

Second, I had built the mkufs, which is part of ufs-linux.  
see http://ufs-linux.sourceforge.net/,
(I had to apply a patch of Evgeniy Dushistov
after some comaplint of Andrew Morton
regarding ufs support in linux)
see :
http://lkml.org/lkml/2006/5/20/48

Than I had tried the following series of actions:

dd if=/dev/zero of=/test/disk-image count=10240
    => 10240+0 records in
  => 10240+0 records out

cd /work/src/ufs- tools-0.1
./mkufs /test/disk-image

  => /test/disk-image: 5.0MB (10240 sectors) block size 16384, fragment size 2048
        using 4 cylinder groups of 1.27MB, 81 blks, 192 inodes.
  => super-block backups (for fsck -b #) at:
   160, 2752, 5344, 7936

mount -o loop -t ufs  /test/disk-image /loopDir

I get:
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)

why ? Did anyone succeeded with creating and mounting ufs
on a loopback device on linux ?

Dan

Reply via email to