Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*badly\s+destroyed\s+XFS\s+\(on\s+LVM\)\s+\-\s+how\s+to\s+repair\?\s*$/: 7 ]

Total 7 documents matching your query.

1. badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 12 May 2012 14:49:56 +0200
(This might be an LVM problem, but who knows?) I have here an XFS that was on a server running within a XenServer machine. In the end it existed of 4x 2TB disks: PV /dev/xvdg VG sharestore lvm2 [1.95
/archives/xfs/2012-05/msg00171.html (16,797 bytes)

2. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Date: Sat, 12 May 2012 15:43:22 +0200
Le Sat, 12 May 2012 14:49:56 +0200 vous écriviez: Did you restart the LVM service to reassemble everything properly? So far you've done everything I would have thought of... -- -- Emmanuel Florac | D
/archives/xfs/2012-05/msg00172.html (7,973 bytes)

3. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 12 May 2012 19:16:16 +0200
I even rebooted the server, because a "vgchange -ay" hangs that session. Still after the reboot it does this, I can't go around this. So if lvm is correct, then xfs_repair and xfs_metadump have a pro
/archives/xfs/2012-05/msg00173.html (7,705 bytes)

4. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 12 May 2012 19:33:04 +0200
Another strange thing: I now started a "dd if=/dev/dm-0 of=/dev/null bs 24k". For the first seconds(!), it did nothing, I thought it would hang. Then it started, but it's reading in a strange way: De
/archives/xfs/2012-05/msg00175.html (8,831 bytes)

5. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 14 May 2012 16:54:48 +0200
Am Samstag, 12. Mai 2012, 14:49:56 schrieb Michael Monnerie: Seems like it's an XFS problem - could someone help me here? -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Interne
/archives/xfs/2012-05/msg00180.html (8,460 bytes)

6. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 14 May 2012 10:12:30 -0500
Anything in dmesg? ... You have to mdrestore the metadump before you can point repair it it, so that's not a valid operation. No <later> Considering that the problem began when the block device got r
/archives/xfs/2012-05/msg00181.html (13,176 bytes)

7. Re: badly destroyed XFS (on LVM) - how to repair? (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 15 May 2012 03:13:18 +0200
Am Montag, 14. Mai 2012, 10:12:30 schrieb Eric Sandeen: No, nothing. Not for lvm, not for xfs. Ah, silly me. Right, will try. The problem is that xfs_repair does not at all complain, but when I mount
/archives/xfs/2012-05/msg00186.html (9,555 bytes)


This search system is powered by Namazu