[Top] [All Lists]

Re: Filesystem Consistency Issues

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Filesystem Consistency Issues
From: Federico Sevilla III <jijo@xxxxxxxxxxx>
Date: Tue, 6 Dec 2005 07:49:32 +0800
In-reply-to: <43947977.8070904@xxxxxxx>
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <20051204142506.GE2605@xxxxxxxxxxx> <20051205014137.GA7685@xxxxxxxxxxxxxx> <p734q5nsre6.fsf@xxxxxxxxxxxxx> <43943F3E.5080804@xxxxxxx> <43947977.8070904@xxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Dec 05, 2005 at 11:31:35AM -0600, Eric Sandeen wrote:
> Stephen Lord wrote:
> > XFS runs recovery on a readonly filesystem. It has been doing that
> > for years. There are log messages which come out when recovery runs,
> > you should see them in dmesg or the syslog after boot up.
> Yep. That code has changed a bit but the results should be the same...
> Federico, can you verify that you see the log recovery messages when
> your machines boot up?

    pos01:~# dmesg | grep -i xfs
    SGI XFS with no debug enabled
    XFS mounting filesystem hda1
    Starting XFS recovery on filesystem: hda1 (dev: hda1)
    Ending XFS recovery on filesystem: hda1 (dev: hda1)
    VFS: Mounted root (xfs filesystem) readonly.

So the logs "advertise" that log recovery is done. However, "ghost" disk
usage continues to increase until the disks are full, and this can only
be fixed first by mounting the filesystem read-write using a rescue
system, which partially recovers free space, and then by running
xfs_repair which recovers the rest.

 --> Jijo

Federico Sevilla III : jijo.free.net.ph : When we speak of free software
GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price.

<Prev in Thread] Current Thread [Next in Thread>