Messages in this thread |  | | Date | Wed, 11 Sep 1996 22:17:08 +0200 | From | Pierre Habraken <> | Subject | Can't fsck e2fs on loop device |
| |
I am using a loopback device for building a compressed file system. The loop device is configured as a module in a kernel 2.0.18.
When I fsck /tmp/rootfsfile, the file which contains my loop file system, I get:
# fsck -v /tmp/rootfsfile Parallelizing fsck version 0.5b (14-Feb-95) e2fsck 0.5b, 14-Feb-95 for EXT2 FS 0.5a, 95/03/19 /tmp/rootfsfile is clean, no check. #
If I fsck /mnt after having mounted the loop file system there (using mount-2.5k), I get:
# fsck -v /mnt Parallelizing fsck version 0.5b (14-Feb-95) e2fsck 0.5b, 14-Feb-95 for EXT2 FS 0.5a, 95/03/19 fsck.ext2: Is a directory while trying to open /mnt
The filesystem superblock is corrupt. Try running e2fsck with an alternate superblock using the -b option. (8193 is commonly an alternate superblock; Hence, 'e2fsck -b 8193 <device>' may recover the filesystem.) #
I also get this error message when I fsck /dev/ram which hosts my compressed file system.
Any idea about this strange behavior ?
-- -------------------------------------------------------- Pierre HABRAKEN e-mail : Pierre.Habraken@imag.fr --------------------------------------------------------
|  |