xfs
[Top] [All Lists]

XFS umount issue

To: xfs-oss <xfs@xxxxxxxxxxx>
Subject: XFS umount issue
From: Nuno Subtil <subtil@xxxxxxxxx>
Date: Mon, 23 May 2011 14:39:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=GEyW/BMIScos4FNbBRda0X9t7HNGFuslhKW9bNuC+q4=; b=CJk7bTTvQHhoLw4Pz4GjACTsib5iuBtL1nuveh74cbCGjVCkjoL1DflGK5i2QQosl6 Ii5YXwjEM6LE4SB3t0L19AjfNrHes9R14Isxbt8gVHQZjuewIUaDGhteiGWxXIjOEMUP dg/dGBJCNBoYhfRupkTqGL7lGENsYl1ZYYAOE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=GwhmELlnVzfkMMsfPCg6ck7m+56FQ4KR9vtLPyfoG9v0QmKRdIHDmrMD22ZTt6EYez S4NlUWt2kiWDLA1015JfQZPbNpe4mlOFavBJ1iPO6rKgKNwYoReAVKEKAxLXNHtxBCjb LSAB/4lT+J9MaArmSxvcx1FGnZB84o6aRmxjk=
I have an MD RAID-1 array with two SATA drives, formatted as XFS.
Occasionally, doing an umount followed by a mount causes the mount to
fail with errors that strongly suggest some sort of filesystem
corruption (usually 'bad clientid' with a seemingly arbitrary ID, but
occasionally invalid log errors as well).

The one thing in common among all these failures is that they require
xfs_repair -L to recover from. This has already caused a few
lost+found entries (and data loss on recently written files). I
originally noticed this bug because of mount failures at boot, but
I've managed to repro it reliably with this script:

while true; do
        mount /store
        (cd /store && tar xf test.tar)
        umount /store
        mount /store
        rm -rf /store/test-data
        umount /store
done

test.tar contains around 100 files with various sizes inside
test-data/, ranging from a few hundred KB to around 5-6MB. The failure
triggers within minutes of starting this loop.

I'm not entirely sure that this is XFS-specific, but the same script
does run successfully overnight on the same MD array with ext3 on it.
This is on an ARM system running kernel 2.6.39.

Has something like this been seen before?

Thanks,
Nuno

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