Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*catch22\:\s+xfs_repair\s+fails\,\s+tells\s+me\s+to\s+mount\,\s+which\s+fails\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*catch22\:\s+xfs_repair\s+fails\,\s+tells\s+me\s+to\s+mount\,\s+which\s+fails\s*$/: 10 ]

Total 10 documents matching your query.

1. catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author:; Date: Wed, 30 Aug 2006 09:24:11 +0100; this morning I woke up to a system without /home, the reason being: piper:~# mount /dev/mapper/vg0-home [308] mount: Unknown error 990 piper:~# dmesg | tail -20 [32,309] Starting XFS recovery on fil; /archives/xfs/2006-08/msg00227.html (11,253 bytes)
2. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author:; Date: Wed, 30 Aug 2006 13:41:09 +0200; FYI, here is how I fixed it, using LVM snapshots to ensure that xfs_repair -L would produce acceptable results: http://blog.madduck.net/geek/2006.08.30-lvm-for-filesystem-recovery I'd still be intere; /archives/xfs/2006-08/msg00228.html (8,789 bytes)
3. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author:; Date: Wed, 30 Aug 2006 19:21:53 +0530; Hi Martin, In this particular case, the log written is corrupted. That's why, forcing to make the inode going corrupt would not help. The real issue is why log content is not valid. By any chance, di; /archives/xfs/2006-08/msg00229.html (12,852 bytes)
4. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author:; Date: Wed, 30 Aug 2006 16:15:48 +0200; also sprach Shailendra Tripathi <stripathi@xxxxxxxxx> [2006.08.30.1551 +0200]: No, definitely not. Thanks for the info. I managed to restore the filesystem with xfs_repair -L in the mean time (see fo; /archives/xfs/2006-08/msg00230.html (9,275 bytes)
5. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author:; Date: Wed, 30 Aug 2006 14:15:39 -0500; martin f krafft wrote: Btw: there's the xfs and linux-xfs mailing list, and I am confused about whether they're separate or merged, and which one I should be using. If you have any input, I'd love to; /archives/xfs/2006-08/msg00231.html (8,696 bytes)
6. catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author: >; Date: Wed, 30 Aug 2006 09:24:11 +0100; this morning I woke up to a system without /home, the reason being: piper:~# mount /dev/mapper/vg0-home [308] mount: Unknown error 990 piper:~# dmesg | tail -20 [32,309] Starting XFS recovery on fil; /archives/xfs/2006-08/msg00479.html (11,253 bytes)
7. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author: >; Date: Wed, 30 Aug 2006 13:41:09 +0200; FYI, here is how I fixed it, using LVM snapshots to ensure that xfs_repair -L would produce acceptable results: http://blog.madduck.net/geek/2006.08.30-lvm-for-filesystem-recovery I'd still be intere; /archives/xfs/2006-08/msg00480.html (8,789 bytes)
8. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author: >; Date: Wed, 30 Aug 2006 19:21:53 +0530; Hi Martin, In this particular case, the log written is corrupted. That's why, forcing to make the inode going corrupt would not help. The real issue is why log content is not valid. By any chance, di; /archives/xfs/2006-08/msg00481.html (12,852 bytes)
9. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author: >; Date: Wed, 30 Aug 2006 16:15:48 +0200; also sprach Shailendra Tripathi <stripathi@xxxxxxxxx> [2006.08.30.1551 +0200]: No, definitely not. Thanks for the info. I managed to restore the filesystem with xfs_repair -L in the mean time (see fo; /archives/xfs/2006-08/msg00482.html (9,275 bytes)
10. Re: catch22: xfs_repair fails, tells me to mount, which fails (score: 1): Author: >; Date: Wed, 30 Aug 2006 14:15:39 -0500; martin f krafft wrote: Btw: there's the xfs and linux-xfs mailing list, and I am confused about whether they're separate or merged, and which one I should be using. If you have any input, I'd love to; /archives/xfs/2006-08/msg00483.html (8,696 bytes)

Current List: 1 - 10
Page: [1]