Skip to contentSkip to conversation

Weird message from xfs_repair

DISCUSSION Emmanuel Florac 3 participants 4 messages May 1, 2013 – May 2, 2013

lore
Share & tools
lore
#0 lore raw

Hi everyone,

I've just had to resort to the latest devel version of xfs_repair to get back some heavily damaged filesystem (thanks to a failing RAID controller), and it ended with the following message:

cache_purge: shake on cache 0x672030 left 1 nodes!?

What's this about? I didn't look at the source, but a new run of xfs_repair detected nothing.

Signature · 11 lines
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<[email protected]>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
#1 lore raw

Hi Emmanuel,

Quoted 8 lines · Emmanuel Florac

I've just had to resort to the latest devel version of xfs_repair to get back some heavily damaged filesystem (thanks to a failing RAID controller), and it ended with the following message:

cache_purge: shake on cache 0x672030 left 1 nodes!?

What's this about? I didn't look at the source, but a new run of xfs_repair detected nothing.

xfs_repair/libxfs has caches for xfs_bufs and inodes to speed things up. cache_purge is trying to flush out all entries from one of those caches. After the purge one entry was left unexpectedly, maybe because someone leaked a reference on it or something. The message doesn't indicate an on-disk problem, it's a problem in xfs_repair.

Regards,
Ben

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#2 lore raw
Quoted 9 lines · Ben Myers

Hi Emmanuel,

Quoted 6 lines · Emmanuel Florac

I've just had to resort to the latest devel version of xfs_repair to get back some heavily damaged filesystem (thanks to a failing RAID controller), and it ended with the following message:

cache_purge: shake on cache 0x672030 left 1 nodes!?

Quoted 8 lines
Quoted 2 lines

What's this about? I didn't look at the source, but a new run of xfs_repair detected nothing.

xfs_repair/libxfs has caches for xfs_bufs and inodes to speed things up. cache_purge is trying to flush out all entries from one of those caches. After the purge one entry was left unexpectedly, maybe because someone leaked a reference on it or something. The message doesn't indicate an on-disk problem, it's a problem in xfs_repair.

Several of those internal cache housekeeping messages can be alarming. Indeed anything out of the ordinary during repair is alarming to most users. ;)

At any rate they're completely useless to the administrator. We should consider a way to reassure the user, and make them useful at the same time.

Maybe a global set when something like this happens, and then at the end, a friendly message about what it meant and how to report the error and/or help debug?

Although if repair is done now, it's probably unlikely(?) that the message would pop out again, so is there really anything which could be done at this point?

Emmanuael - if another xfs_repair pops out the same error, then capturing a metadump of the fs would probably let someone look into it. Someone who has time, that is. ;)

-Eric

Quoted 7 lines

Ben

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

#3 lore raw

Le Wed, 01 May 2013 15:58:09 -0500 vous écriviez:

Quoted 4 lines

Several of those internal cache housekeeping messages can be alarming. Indeed anything out of the ordinary during repair is alarming to most users. ;)

Well I've had xfs_repair happily wiping several terabytes of data in the past, so I'm easily concerned :) But I supposed this is mostly related to the fact I was running a pre-release.

Quoted 3 lines

Emmanuael - if another xfs_repair pops out the same error, then capturing a metadump of the fs would probably let someone look into it. Someone who has time, that is. ;)

In that case the filesystem was in extremely poor shape with lots of errors I've never seen before, and a lot of users waiting for it to come back online. Fortunately recent xfs_repair seem to be reliable enough.

Signature · 11 lines
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<[email protected]>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs