All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs file system in process of becoming corrupt; though	xfs_repair	thinks it's fine! ; -/ (was xfs_dump problem...)
Date: Tue, 29 Jun 2010 19:45:21 -0700	[thread overview]
Message-ID: <4C2AAFC1.9080708@tlinx.org> (raw)
In-Reply-To: <20100630011647.GD24712@dastard>

To make matters more interesting -- xfsdump can't access a couple of
files and a directory or two.

It thinks they are 'stale NFS handles' (I'm not running any NFS 
file systems).

in @  0.0 kB/s, out @  0.0 kB/s,  0.0 kB total, buffer   0% fullxfsdump: WARNING: unable to open directory: ino 2082342: Stale NFS file handle
xfsdump: WARNING: unable to open directory: ino 2082343: Stale NFS file handle
in @ 4079 kB/s, out @ 4079 kB/s, 2040 kB total, buffer   0% fullxfsdump: dumping non-directory files
in @ 68.0 MB/s, out @ 68.0 MB/s, 1209 GB total, buffer   0% fullll
in @  107 MB/s, out @  105 MB/s, 2200 GB total, buffer   0% fullxfsdump: ending media file
xfsdump: media file size 2362017678616 bytes
xfsdump: dump size (non-dir files) : 2361953613176 bytes
xfsdump: dump complete: 10926 seconds elapsed
xfsdump: Dump Status: SUCCESS

Running xfs_db on the file system (finished dumping)
a block get returns:
dir 1133368 block 0 extra leaf entry 5438b33d 79
dir 1133368 block 0 extra leaf entry 6624beba 71
dir 1133368 block 0 extra leaf entry 6d832f88 69
dir 1133368 block 0 extra leaf entry e6279e2d 80
dir ino 1133368 missing leaf entry for e627de2d/80
dir ino 1133368 missing leaf entry for 7624beba/71
dir ino 1133368 missing leaf entry for 5418b33d/79
dir ino 1133368 missing leaf entry for 6d832f80/69
dir 1134347 block 0 extra leaf entry 3907754f 4e
dir 1134347 block 0 extra leaf entry 3cae5257 47
dir 1134347 block 0 extra leaf entry 6e3a4cfb 40
dir ino 1134347 missing leaf entry for 6e38ccfb/40
dir ino 1134347 missing leaf entry for 3905f54f/4e
dir ino 1134347 missing leaf entry for 3cacd257/47
dir 1149453 block 0 extra leaf entry 190f789f 7d
dir ino 1149453 missing leaf entry for 190b78df/7d
dir 1193988 block 0 extra leaf entry 8f2b7b0c 80
dir ino 1193988 missing leaf entry for 8d2b7b0c/80
dir 2098474 block 0 extra leaf entry 891d210e b5
dir ino 2098474 missing leaf entry for 891d200f/b5
dir 2103050 block 0 extra leaf entry 3c8b96be 79
dir ino 2103050 missing leaf entry for 3c8b96ae/79
dir 2106377 block 0 extra leaf entry 6554830e 185
dir 2106377 block 0 extra leaf entry 8265fcda 173
dir 2106377 block 0 extra leaf entry b251fcda 17f
dir 2106377 block 0 extra leaf entry b687730b 179
dir ino 2106377 missing leaf entry for 8265fcd2/173
dir ino 2106377 missing leaf entry for b251fcd2/17f
dir ino 2106377 missing leaf entry for b687734b/179
dir ino 2106377 missing leaf entry for 6554c31e/185
dir 2107395 block 0 extra leaf entry 207fea65 ff
dir 2107395 block 0 extra leaf entry dd1d75a2 f8
dir ino 2107395 missing leaf entry for df1d75a2/f8
dir ino 2107395 missing leaf entry for 206fea65/ff
dir 2215937 block 0 extra leaf entry 1d5bcd6d 3a
dir 2215937 block 0 extra leaf entry 9c82da3c 9c
dir 2215937 block 0 extra leaf entry ff88d238 a4
dir ino 2215937 missing leaf entry for 1f5bcd6d/3a
dir ino 2215937 missing leaf entry for fd88d238/a4
dir ino 2215937 missing leaf entry for 9e82da3c/9c
dir 2218278 block 0 extra leaf entry 1d5bcd6d 3a
dir 2218278 block 0 extra leaf entry 9c82da3c 9c
dir 2218278 block 0 extra leaf entry ff88d238 a4
dir ino 2218278 missing leaf entry for 1f5bcd6d/3a
dir ino 2218278 missing leaf entry for fd88d238/a4
dir ino 2218278 missing leaf entry for 9e82da3c/9c
dir 2241309 block 0 extra leaf entry 51ae209 39
dir 2241309 block 0 extra leaf entry b5c3baca 32
dir ino 2241309 missing leaf entry for 5186209/39
dir ino 2241309 missing leaf entry for b5c13aca/32
dir 2291983 block 0 extra leaf entry 16650e73 117
dir 2291983 block 0 extra leaf entry 355a317c 112
dir 2291983 block 0 extra leaf entry 47464246 ee
dir 2291983 block 0 extra leaf entry 620ec6fb 109
dir 2291983 block 0 extra leaf entry 62170366 e7
dir 2291983 block 0 extra leaf entry 73c17bba 10d
dir 2291983 block 0 extra leaf entry 747a8790 e2
dir 2291983 block 0 extra leaf entry 894504e3 ff
dir 2291983 block 0 extra leaf entry b17d4203 11c
dir 2291983 block 0 extra leaf entry d12c165b 105
dir 2291983 block 0 extra leaf entry d33f483d fb
dir 2291983 block 0 extra leaf entry e28ebb3b f2
dir 2291983 block 0 extra leaf entry f9f9b6d1 f6
dir ino 2291983 missing leaf entry for 8b4504e3/ff
dir ino 2291983 missing leaf entry for d33f48ad/fb
dir ino 2291983 missing leaf entry for 375a317c/112
dir ino 2291983 missing leaf entry for e9f9bed1/f6
dir ino 2291983 missing leaf entry for 45464246/ee
dir ino 2291983 missing leaf entry for 71c17bba/10d
dir ino 2291983 missing leaf entry for b13d4203/11c
dir ino 2291983 missing leaf entry for 745a8790/e2
dir ino 2291983 missing leaf entry for 16650e63/117
dir ino 2291983 missing leaf entry for e21f0366/e7
dir ino 2291983 missing leaf entry for e08ebb2b/f2
dir ino 2291983 missing leaf entry for d12896db/105
dir ino 2291983 missing leaf entry for 620ec6eb/109

xfs_repair -n now shows:

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 2
        - agno = 1
        - agno = 0
        - agno = 5
        - agno = 4
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
entry "10 Otome ha DO MY BEST desho¿ (off vocal).flac" (ino 2359102) in dir 1133368 is a duplicate name, would junk entry
entry "06 Otome ha DO MY BEST desho¿ Otome ver..flac" (ino 2359100) in dir 1133368 is a duplicate name, would junk entry
entry "05 Otome ha DO MY BEST desho¿ Hime ver..flac" (ino 2359099) in dir 1133368 is a duplicate name, would junk entry
entry "04 Otome ha DO MY BEST desho¿ 2007ver..flac" (ino 2359086) in dir 1133368 is a duplicate name, would junk entry
entry "04 Finality blue «instrumental».flac" (ino 2220801) in dir 1134347 is a duplicate name, would junk entry
entry "06 Koko ni Atta ne «instrumental».flac" (ino 2220800) in dir 1134347 is a duplicate name, would junk entry
entry "05 Heart All Green «instrumental».flac" (ino 2359103) in dir 1134347 is a duplicate name, would junk entry
entry "01_Tenkai Hen Josô e no Zensô Kyoku.mp3" (ino 2359093) in dir 1149453 is a duplicate name, would junk entry
entry "01 Träumerei.flac" (ino 2359098) in dir 1193988 is a duplicate name, would junk entry
entry "16 - Pretty Guardian Sailor Moon - Kiss!² Bang!².ogg" (ino 2359097) in dir 2098474 is a duplicate name, would junk entry
entry "03 Broken MÖBIUS.ogg" (ino 2359094) in dir 2103050 is a duplicate name, would junk entry
entry "14 - Broken MÖBIUS Henkei A.ogg" (ino 2359095) in dir 2106377 is a duplicate name, would junk entry
entry "27 - Shin·Henshin Sailormoon.ogg" (ino 2359092) in dir 2106377 is a duplicate name, would junk entry
entry "19 - Broken MÖBIUS Henkei B.ogg" (ino 2359088) in dir 2106377 is a duplicate name, would junk entry
entry "06 - GURU·GURU·GURA.ogg" (ino 2359089) in dir 2106377 is a duplicate name, would junk entry
entry "35 Ankoku no Uranai Noshi · Lilith.ogg" (ino 2359091) in dir 2107395 is a duplicate name, would junk entry
entry "17 Kaguya Shima·Mukashi Mono Gatarii.ogg" (ino 2359087) in dir 2107395 is a duplicate name, would junk entry
bad hash table for directory inode 2215937 (hash value mismatch): would rebuild
bad hash table for directory inode 2218278 (hash value mismatch): would rebuild
entry "03 Free and Dream «Instrumental».flac" (ino 2359090) in dir 2241309 is a duplicate name, would junk entry
entry "04 Asu he -Sorairo no Tegami- «Instrumental».flac" (ino 2359096) in dir 2241309 is a duplicate name, would junk entry
entry "18 Rafraîchissement.flac" (ino 2359085) in dir 2291983 is a duplicate name, would junk entry
entry "17 Différent malgré la ressemblance.flac" (ino 2218273) in dir 2291983 is a duplicate name, would junk entry
entry "09 Sincèrement.flac" (ino 2218271) in dir 2291983 is a duplicate name, would junk entry
entry "15 Déjà Vu.flac" (ino 2218276) in dir 2291983 is a duplicate name, would junk entry
entry "20 Fête d'école.flac" (ino 2218275) in dir 2291983 is a duplicate name, would junk entry
entry "12 Péripétie.flac" (ino 2218270) in dir 2291983 is a duplicate name, would junk entry
entry "27 Lieu de la bataille décisive.flac" (ino 2218272) in dir 2291983 is a duplicate name, would junk entry
entry "06 Sérénité.flac" (ino 2218274) in dir 2291983 is a duplicate name, would junk entry
entry "04 Tragédie.flac" (ino 2218266) in dir 2291983 is a duplicate name, would junk entry
entry "25 Serment éternel.flac" (ino 2218268) in dir 2291983 is a duplicate name, would junk entry
entry "16 Force étrange.flac" (ino 2218277) in dir 2291983 is a duplicate name, would junk entry
entry "28 Manoeuvres secrètes.flac" (ino 2218269) in dir 2291983 is a duplicate name, would junk entry
entry "26 Jours passés.flac" (ino 2218267) in dir 2291983 is a duplicate name, would junk entry
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 2218266, would move to lost+found
disconnected inode 2218267, would move to lost+found
disconnected inode 2218268, would move to lost+found
disconnected inode 2218269, would move to lost+found
disconnected inode 2218270, would move to lost+found
disconnected inode 2218271, would move to lost+found
disconnected inode 2218272, would move to lost+found
disconnected inode 2218273, would move to lost+found
disconnected inode 2218274, would move to lost+found
disconnected inode 2218275, would move to lost+found
disconnected inode 2218276, would move to lost+found
disconnected inode 2218277, would move to lost+found
disconnected inode 2220800, would move to lost+found
disconnected inode 2220801, would move to lost+found
disconnected inode 2359085, would move to lost+found
disconnected inode 2359086, would move to lost+found
disconnected inode 2359087, would move to lost+found
disconnected inode 2359088, would move to lost+found
disconnected inode 2359089, would move to lost+found
disconnected inode 2359090, would move to lost+found
disconnected inode 2359091, would move to lost+found
disconnected inode 2359092, would move to lost+found
disconnected inode 2359093, would move to lost+found
disconnected inode 2359094, would move to lost+found
disconnected inode 2359095, would move to lost+found
disconnected inode 2359096, would move to lost+found
disconnected inode 2359097, would move to lost+found
disconnected inode 2359098, would move to lost+found
disconnected inode 2359099, would move to lost+found
disconnected inode 2359100, would move to lost+found
disconnected inode 2359102, would move to lost+found
disconnected inode 2359103, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

-------------
This isn't going to help to repair it though -- I repaired it this
morning and it showed up as fine!

Then all of the above happened today!

It would appear that 2.6.34 might have some problems in it?

-linda

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-06-30  2:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27  1:10 WARNING xfsdump [still] Cannot allocate memory for list of [root|non-root] attributes for nondir ino xxyz Linda A. Walsh
2010-06-28  2:27 ` Dave Chinner
2010-06-29 22:33   ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Linda Walsh
2010-06-29 23:25     ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-29 23:55       ` Michael Weissenbacher
2010-06-30  0:42         ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30  1:16           ` Dave Chinner
2010-06-30  2:45             ` Linda A. Walsh [this message]
2010-07-01 23:58               ` Dave Chinner
2010-07-07  3:18                 ` Linda A. Walsh
2010-07-07  5:56                   ` Linda Walsh
2010-07-07  6:36                     ` Dave Chinner
2010-07-07  9:30                       ` Linda A. Walsh
2010-07-07 21:01                         ` Linda Walsh
2010-06-30  0:01       ` Linda A. Walsh
2010-06-30  1:06         ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-30  1:52           ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 21:01             ` Stan Hoeppner
2010-07-07 21:40               ` utf-8' chars from Winxp machine may be problem related (was Re: xfs file system in process of becoming corrupt; though xfs_repair...) Linda A. Walsh
2010-07-07 23:40                 ` Stan Hoeppner
2010-07-08  0:38                   ` Linda A. Walsh
2010-06-30 18:25     ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Michael Monnerie
2010-06-30 23:30       ` rsync and corrupt inodes (was xfs_dump problem) Dave Chinner
2010-07-01  8:25         ` Michael Monnerie
2010-07-02  2:42           ` Dave Chinner
2010-07-02  6:21             ` Michael Monnerie
2010-07-04 22:53               ` Dave Chinner
2010-07-12 11:28                 ` Michael Monnerie
2010-07-07 21:56         ` Linda Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C2AAFC1.9080708@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.