Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*corruption\s+issue\s*$/: 10 ]

Total 10 documents matching your query.

1. corruption issue (score: 1)
Author: Christian Rice <xian@xxxxxxxxxxx>
Date: Thu, 15 Aug 2002 15:41:47 -0700
I'm wondering if this is a recoverable situation: [root@ozu root]# xfs_repair /dev/hdb3 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 inconsistent with calculated v
/archives/xfs/2002-08/msg00229.html (8,498 bytes)

2. Re: corruption issue (score: 1)
Author: Stephen Lord <lord@xxxxxxx>
Date: 15 Aug 2002 19:13:11 -0500
Ugh, so you actually ran repair on the filesystem here by the look of it. Those values in the super block are very strange, 18446744073709551615 is -1 as a 64 bit value. Hopefully the dirty log preve
/archives/xfs/2002-08/msg00230.html (10,747 bytes)

3. Re: corruption issue (score: 1)
Author: Christian Rice <xian@xxxxxxxxxxx>
Date: Thu, 15 Aug 2002 18:53:39 -0700
Yeah, I ran xfs_repair on it after trying a mount and getting the usual: [root@ozu tmp]# mount -t xfs /dev/hdb3 /hdb3 mount: wrong fs type, bad option, bad superblock on /dev/hdb3, or too many mounte
/archives/xfs/2002-08/msg00232.html (13,642 bytes)

4. Re: corruption issue (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Thu, 15 Aug 2002 22:38:58 -0500 (CDT)
Christian - Do you have any idea what the true error was behind mount's very unhelpful error message? It would be in the system logs. I suppose it was a recovery error, but it might be interesting to
/archives/xfs/2002-08/msg00234.html (7,828 bytes)

5. Re: corruption issue (score: 1)
Author: Christian Rice <xian@xxxxxxxxxxx>
Date: Fri, 16 Aug 2002 10:07:04 -0700
As a matter of fact, the system log shows this when I try to mount: Aug 16 10:05:51 ozu kernel: XFS mounting filesystem ide0(3,67) Aug 16 10:05:52 ozu kernel: XFS: nil uuid in log - IRIX style log Au
/archives/xfs/2002-08/msg00254.html (8,689 bytes)

6. corruption issue (score: 1)
Author:
Date: Thu, 15 Aug 2002 15:41:47 -0700
I'm wondering if this is a recoverable situation: [root@ozu root]# xfs_repair /dev/hdb3 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 inconsistent with calculated v
/archives/xfs/2002-08/msg00816.html (8,498 bytes)

7. Re: corruption issue (score: 1)
Author:
Date: 15 Aug 2002 19:13:11 -0500
Ugh, so you actually ran repair on the filesystem here by the look of it. Those values in the super block are very strange, 18446744073709551615 is -1 as a 64 bit value. Hopefully the dirty log preve
/archives/xfs/2002-08/msg00817.html (10,747 bytes)

8. Re: corruption issue (score: 1)
Author:
Date: Thu, 15 Aug 2002 18:53:39 -0700
Yeah, I ran xfs_repair on it after trying a mount and getting the usual: [root@ozu tmp]# mount -t xfs /dev/hdb3 /hdb3 mount: wrong fs type, bad option, bad superblock on /dev/hdb3, or too many mounte
/archives/xfs/2002-08/msg00819.html (13,642 bytes)

9. Re: corruption issue (score: 1)
Author:
Date: Thu, 15 Aug 2002 22:38:58 -0500 (CDT)
Christian - Do you have any idea what the true error was behind mount's very unhelpful error message? It would be in the system logs. I suppose it was a recovery error, but it might be interesting to
/archives/xfs/2002-08/msg00821.html (7,828 bytes)

10. Re: corruption issue (score: 1)
Author:
Date: Fri, 16 Aug 2002 10:07:04 -0700
As a matter of fact, the system log shows this when I try to mount: Aug 16 10:05:51 ozu kernel: XFS mounting filesystem ide0(3,67) Aug 16 10:05:52 ozu kernel: XFS: nil uuid in log - IRIX style log Au
/archives/xfs/2002-08/msg00841.html (8,689 bytes)


This search system is powered by Namazu