On Thu, 27 Oct 2016 18:03:24 -0700 John Andersen <jsamyth@gmail.com> wrote:
I have a /home partition using luks on xfs
I've got two little files that barfed up errors while running a backup. Any attempt to access these files results in an error:
poulsbo:/home # l ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff ls: cannot access ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff: Structure needs cleaning
If I list the entire directory I get this:
poulsbo:/home # l ./jsa/.cache/google-chrome/Default/old_Cache_000/ ls: cannot access ./jsa/.cache/google-chrome/Default/old_Cache_000/f_0259ff: Structure needs cleaning total 70772 drwx------ 2 jsa users 94208 May 31 12:38 ./ drwx------ 5 jsa users 59 Jun 2 14:37 ../ -rw------- 1 jsa users 10231808 May 31 12:31 data_4 ...snip -rw------- 1 jsa users 32938 Feb 14 2016 f_020630 -????????? ? ? ? ? ? f_0259ff -rw------- 1 jsa users 33622 Mar 17 2016 f_025fef
Over on the XFS site Faq them mumble something about question marks in the directory listing suggest you might need inode64, but its only a 500gig drive and this seems unwise at this poing.
These also dumped the following into my log:
Oct 27 17:37:20 poulsbo.homeip.net kernel: XFS (dm-1): xfs_iread: validation failed for inode 537556822 failed Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc00: 49 4e 81 80 03 02 00 00 00 00 03 e8 00 00 00 64 IN.............d Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc10: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc20: 56 e9 94 78 12 00 ec 9f 56 e9 94 78 12 10 2e c5 V..x....V..x.... Oct 27 17:37:20 poulsbo.homeip.net kernel: ffff8800a928fc30: 56 e9 94 78 12 10 2e c5 00 00 00 00 00 02 72 5d V..x..........r] Oct 27 17:37:20 poulsbo.homeip.net kernel: XFS (dm-1): Internal error xfs_iread at line 392 of file ../fs/xfs/xfs_inode_buf.c. Caller xfs_iget+0x298/0x7f0 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: CPU: 1 PID: 16839 Comm: ls Not tainted 3.16.7-45-desktop #1 Oct 27 17:37:21 poulsbo.homeip.net kernel: Hardware name: Dell Inc. MP061 /0YD479, BIOS A08 04/02/2007 Oct 27 17:37:21 poulsbo.homeip.net kernel: 0000000000000001 ffffffff8161e1f6 ffff8800a203f000 ffffffffa07e506b Oct 27 17:37:21 poulsbo.homeip.net kernel: 00000188ba9be7c0 ffffffffa07eadb8 ffff88001f091400 ffff8800a203f000 Oct 27 17:37:21 poulsbo.homeip.net kernel: 0000000000000075 0000000000000000 ffffffffa0832eba ffffffffa07eadb8 Oct 27 17:37:21 poulsbo.homeip.net kernel: Call Trace: Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff810051ee>] dump_trace+0x8e/0x350 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81006aa1>] show_stack+0x21/0x50 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff8161e1f6>] dump_stack+0x49/0x6a Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07e506b>] xfs_corruption_error+0x5b/0x80 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa0832eba>] xfs_iread+0xea/0x400 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07eadb8>] xfs_iget+0x298/0x7f0 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa082cf2e>] xfs_lookup+0xee/0x110 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffffa07f0306>] xfs_vn_lookup+0x56/0xa0 [xfs] Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c1a59>] lookup_real+0x19/0x50 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c234f>] __lookup_hash+0x2f/0x40 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff8161b550>] lookup_slow+0x3e/0xa3 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c52a5>] path_lookupat+0x725/0x790 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c5336>] filename_lookup+0x26/0xc0 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811c8b54>] user_path_at_empty+0x54/0x90 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811bd2d6>] vfs_fstatat+0x46/0x90 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff811bd7ad>] SYSC_newlstat+0x1d/0x40 Oct 27 17:37:21 poulsbo.homeip.net kernel: [<ffffffff81624f0d>] system_call_fastpath+0x1a/0x1f Oct 27 17:37:21 poulsbo.homeip.net kernel: [<00007fecc5b6dd35>] 0x7fecc5b6dd34 Oct 27 17:37:21 poulsbo.homeip.net kernel: XFS (dm-1): Corruption detected. Unmount and run xfs_repair
So I did as directed, unmounted it and ran xfs_repair on the /dev/mapper/cr_yaddayadda device that represents the encrypted partition /dev/sda4.
(it is said to be pointless and dangerous to run xfs_repair on the actual underlying device. Is this true? Its still xfs underneath is it not? ).
XFS underneath the crypto? That sounds pretty ridiculous does it not?
After multiple such runs, no error is found by xfs_repair, and the problem is not repaired.
smartctl shows no errors and no sectors having been re-mapped. The drive appears physically fine.
So how do I proceed from here? I have two such little files that barf in the log each time I even try to peek at them.
Either ignore those two files and replace them from your backup, or take the symptoms to the XFS mailing list would be my suggestion. I seem to remember they have a document on what evidence to supply when reporting a problem, and they react well if you do that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org