Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Aug 2004 21:56:25 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i7B4uLCc004941 for ; Tue, 10 Aug 2004 21:56:21 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.13.0/8.12.8/Submit) id i7B4uLXD004937 for linux-xfs@oss.sgi.com; Tue, 10 Aug 2004 21:56:21 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i7B4uIGR004896 for ; Tue, 10 Aug 2004 21:56:19 -0700 Received: (from apache@localhost) by oss.sgi.com (8.13.0/8.12.8/Submit) id i7B47qpE003320; Tue, 10 Aug 2004 21:07:52 -0700 Date: Tue, 10 Aug 2004 21:07:52 -0700 Message-Id: <200408110407.i7B47qpE003320@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 355] New: unreplayable log after crash X-Bugzilla-Reason: AssignedTo X-archive-position: 3890 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2387 Lines: 72 http://oss.sgi.com/bugzilla/show_bug.cgi?id=355 Summary: unreplayable log after crash Product: Linux XFS Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: Peter.Kelemen+sgi@cern.ch I have a ~700G filesystem that experienced a hard crash (controller failure), but the subsequent mount fails when the log would be replayed. xfs_check tells me that the filesystem is funky: bad magic # 0x421cd4bf in inode 11281887 bmbt block 66/1011263 expected level 0 got 6369 in inode 11281887 bmbt block 66/1011263 bad btree nrecs (13911, min=127, max=254) in inode 11281887 bmap block 70217279 extent count for ino 11281887 data fork too low (0) for file format bad nblocks 7169 for inode 11281887, counted 1 bad nextents 28 for inode 11281887, counted 0 bad nblocks 67585 for inode 11317715, counted 67073 bad nextents 155 for inode 11317715, counted 154 bad nblocks 98817 for inode 11343754, counted 99329 bad nextents 242 for inode 11343754, counted 244 bad nblocks 52737 for inode 11343803, counted 53761 bad nextents 185 for inode 11343803, counted 189 bad nblocks 24577 for inode 11358383, counted 24065 bad nextents 71 for inode 11358383, counted 68 ... mount says mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many mounted file systems ...and returns with exit code 32. xfs_repair instructs me to zero the log before attempting a repair. Device is software striped array across two 3ware hardware RAID-5s. Filesystem geometry (info from xfs_db, superblock 0): blocksize = 4096 dblocks = 175829568 agblocks = 1048512 agcount = 168 logblocks = 32768 versionnum = 0x3584 sectsize = 512 inodesize = 512 logsunit = 262144 Compressed xfs_logprint output is available at http://cern.ch/fuji/cruft/md0.logprint.bz2 [1.7 MiB, 57 MiB uncompressed] I'm currently dumping the md0 device to another machine for further analysis. Kernel is 2.4.20-31.7.2.cernsmp which is basically RedHat plus some local patches to the SCSI tape layer. Hardware is dual Xeon 2.4GHz 1G RAM 3ware 7850-8/7500-4, WD 120G disks. Peter ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.