Manuel Bouyer wrote:
> Does fstat report something about /mnt/lala ?

nope.  it reports about it during the extraction, and nothing 
afterwards, accordingly.  and no process is keeping the fs busy.

This also happens when simply stressing the filesystem, e.g. find 
/mnt/lala | grep something.  otherwise (if not stressed enought), it 
unmounts cleanly.

I tryed again, this time safer (ext2 only),

node2# mkdir /mnt/lili
node2# pwd
/xendoms
node2# mkdir lili
node2# cd lili
node2# dd if=/dev/zero of=lili.ext2 bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 33.354 secs (31437788 bytes/sec)
node2# vnconfig -l
vnd0: /xendoms (/dev/wd0e) inode 138245
vnd1: not in use
vnd2: not in use
vnd3: not in use
node2# mkfs.ext2 ./lili.ext2
mke2fs 1.39 (29-May-2006)
./lili.ext2 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)
128000 inodes, 256000 blocks
12800 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=264241152
8 block groups
32768 blocks per group, 32768 fragments per group
16000 inodes per group
Superblock backups stored on blocks:
         32768, 98304, 163840, 229376

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
node2# vnconfig vnd3 ./lili.ext2
node2# mount_ext2fs /dev/vnd3a /mnt/lili
node2# tar xjpf /xendoms/gentoo/stage3-i686-2007.0.tar.bz2 -C /mnt/lili
node2# fstat | grep '/mnt/lili'
node2# umount /mnt/lili
umount: /mnt/lili: Device busy


Thanks
Pierre-Philipp