xfs
[Top] [All Lists]

Re: XFS partition problem

To: linux-xfs@xxxxxxxxxxx
Subject: Re: XFS partition problem
From: evilninja <evilninja@xxxxxxx>
Date: Fri, 25 Jun 2004 13:01:23 +0200
Cc: Raphael Bauduin <raphael.bauduin@xxxxxxxxxxxxxx>
In-reply-to: <40DBE411.60506@xxxxxxxxxxxxxx>
References: <40DAE337.1010109@xxxxxxxxxxxxxx> <40DB1969.5020807@xxxxxxx> <40DBE411.60506@xxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 0.6 (X11/20040605)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Raphael Bauduin schrieb:
>> Dec  3 10:18:19 dotnet kernel: Starting XFS recovery on filesystem:
>> sd(8,38) (dev: 8/38)
>> Dec  3 10:18:19 dotnet kernel: Ending XFS recovery on filesystem:
>> sd(8,38) (dev: 8/38)
>
>> What's the exact meaning of these messages? Does it mean the partition
>> was not cleanly unmounted?

hm, not being an XFS hacker, i'd say: yes, indeed. unmounting & mounting
an XFS here gives:

prinz kernel: XFS mounting filesystem sda8
prinz kernel: Ending clean XFS mount for filesystem: sda8

these "ending XFS recovery" seem to result from "XLOG_RECOVERY_NEEDED"
as seen in fs/xfs/xfs_log_recover.c.

can you boot from a xfs-aware bootdisk, an then try xfs_check *before*
mounting the fs? then, after xfs_check exits (with no errors) you could
mount it again and see, if recovery is still needed.

>> If the partition is not cleanly unmounted at each boot, could it result
>> in a partition error like I had?

i geuss that would be the cause then.

>> Once the problem occured with the 2.4.26, it also accured when booting
>> in 2.4.20

so, your problem does not rely on a specific kernel version.

Christian.
- --
BOFH excuse #316:

Elves on strike. (Why do they call EMAG Elf Magic)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA3AYDC/PVm5+NVoYRAgXDAKCpcfsMVvA7Fd3PfB8G8q8LppKvQwCfcS2l
N4XXbfNXDSexL/QzZbO0GtA=
=p6qj
-----END PGP SIGNATURE-----


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