lkml.org 
[lkml]   [1996]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Can't fsck e2fs on loop device
In article <32371E44.2CF4BBBD@imag.fr> Pierre Habraken
<Pierre.Habraken@imag.fr> writes:

> 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.
> #

That's exactly what you'd expect.

> 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

Of course. /mnt is a firectory, not a block device or normal file.
You need to run fsck on the underlying source of the filesystem ---
ie, on /tmp/rootfsfile. fsck lets you specify the name of the
filesystem mount point instead as a short cut, but only if the
filesystem is mentioned in /etc/fstab.

> I also get this error message when I fsck /dev/ram which hosts my
> compressed file system.

fsck knows nothing about compressed filesystems!

> Any idea about this strange behavior ?

Nothing strange going on. :)

Cheers,
Stephen.
--
Stephen Tweedie <sct@dcs.ed.ac.uk>
Department of Computer Science, Edinburgh University, Scotland.

\
 
 \ /
  Last update: 2005-03-22 13:38    [W:0.035 / U:8.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site