Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Repair\s+XFS\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Repair\s+XFS\s*$/: 34 ]

Total 34 documents matching your query.

1. Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 13:13:36 -0800; I'm seeing some irregulars halts on one of my XFS volume (/srv). I can only use umount -l to dismount the volume or do a hot reboot. Dec 9 15:47:25 smbserver kernel: xfs_force_shutdown(md(9,5),0x8); /archives/xfs/2003-12/msg00188.html (8,060 bytes)
2. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 13:36:27 -0800; I did try memtest86, but found no problem. I even swapped brand new RAM. Is there more info I can provide? Regards, Norman; /archives/xfs/2003-12/msg00191.html (9,053 bytes)
3. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 16:37:20 -0500; fsck.xfs is a no-op. What you need to do is use xfs_repair on the partition while it is unmounted. Note also that anything in lost+found will be "relost" and then "refound" as xfs_repair just unlinks; /archives/xfs/2003-12/msg00192.html (10,099 bytes)
4. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 13:56:09 -0800; I ran xfs_check /srv but got "xfs_check: can't determine device size". I'm doing something wrong? I can't seem to umount /srv without -l [root@smbserver root]# umount /srv umount: /srv: device is bu; /archives/xfs/2003-12/msg00193.html (10,843 bytes)
5. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 17:26:41 -0500 (EST); How long did you let memtest86 run (# of passes, hours)? It could also be a CPU cache problem, or even the motherboard going flaky. I've also seen some cases of power supply problems being exhibited; /archives/xfs/2003-12/msg00194.html (10,366 bytes)
6. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 17:29:08 -0500; Once you get it unmounted (check that other processes are not using it, you may need to switch to init level 2 or even 1... Anyway, once it is unmounted, you should use: xfs_check /dev/md5 and then t; /archives/xfs/2003-12/msg00195.html (10,216 bytes)
7. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 14:47:30 -0800; Thanks. I will try umounting again and follow your steps after hours. This is a production server 8( I'm just wondering, won't Linux (Mandrake 9.2) do fsck automatically? After each reboot, I do see; /archives/xfs/2003-12/msg00196.html (9,305 bytes)
8. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 14:58:01 -0800; My last memtest86 ran about a good 1/2 to 1 hour, I think it did 3 cycles. I hope it is not HW, as I have 2 other boxes that run exact config except with HW RAID. I'm running Intel SE7500WV2S mother; /archives/xfs/2003-12/msg00197.html (10,575 bytes)
9. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 16:02:26 -0800; On 12/10/03 14:58, Norman Zhang wrote: I'm seeing some irregulars halts on one of my XFS volume (/srv). I can only use umount -l to dismount the volume or do a hot reboot. Dec 9 15:47:25 smbserver ke; /archives/xfs/2003-12/msg00200.html (12,766 bytes)
10. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 16:26:16 -0800; One funny thing, some folders are still viewable after initial stall. Eventually all folders would be not viewable. Anyone seen this? Regards, Norman; /archives/xfs/2003-12/msg00201.html (9,627 bytes)
11. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 19:48:59 -0800; I don't believe that any distro auto-fsck's on XFS partitions.; /archives/xfs/2003-12/msg00202.html (9,238 bytes)
12. Re: Repair XFS (score: 1): Author:; Date: Thu, 11 Dec 2003 11:56:32 +0800; fsck.xfs is a no-op. As mentioned previously, you need to mount then unmount the problemmatic partition, then run xfs_repair(8) manually. For whatever it's worth, I like Knoppix[1] as a rescue disc b; /archives/xfs/2003-12/msg00203.html (9,366 bytes)
13. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 20:10:50 -0800; On 12/10/03 19:48, Joshua Schmidlkofer wrote: I'm just wondering, won't Linux (Mandrake 9.2) do fsck automatically? After each reboot, I do see that it complained system not shutdown properly, press; /archives/xfs/2003-12/msg00204.html (10,301 bytes)
14. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 23:01:03 -0700; --On Wednesday, December 10, 2003 14:47 -0800 Norman Zhang <nzhang@xxxxxxxxxxxxxxx> wrote: Thanks. I will try umounting again and follow your steps after hours. This is a production server 8( I'm jus; /archives/xfs/2003-12/msg00205.html (9,357 bytes)
15. Re: Repair XFS (score: 1): Author:; Date: Thu, 11 Dec 2003 01:04:47 -0600; that's also what the journal's for. xfs_repair is a manual intervention bit because the journal should take care of making the FS sane again. thus the reason XFS, VXFS, EXT3, Reiser and many other ex; /archives/xfs/2003-12/msg00208.html (9,640 bytes)
16. Re: Repair XFS (score: 1): Author:; Date: Wed, 10 Dec 2003 23:57:14 -0900; nice example of why my patch to fsck.xfs should go in. as a reminder: -- xfs_fsck.c.orig Sat Oct 18 19:59:18 2003 +++ xfs_fsck.c Sat Oct 18 20:00:01 2003 @@ -35,8 +35,18 @@ /* This used to be a symli; /archives/xfs/2003-12/msg00209.html (10,328 bytes)
17. Re: Repair XFS (score: 1): Author:; Date: Thu, 11 Dec 2003 11:00:38 -0500; XFS is a journalled file system that, under most all situations, should not need any fsck. Most all distros/init scripts do run FSCK at boot time but for XFS this is not needed and is a no-op. The xf; /archives/xfs/2003-12/msg00217.html (10,370 bytes)
18. Repair XFS (score: 1): Author: >; Date: Wed, 10 Dec 2003 13:13:36 -0800; I'm seeing some irregulars halts on one of my XFS volume (/srv). I can only use umount -l to dismount the volume or do a hot reboot. Dec 9 15:47:25 smbserver kernel: xfs_force_shutdown(md(9,5),0x8); /archives/xfs/2003-12/msg00569.html (8,060 bytes)
19. Re: Repair XFS (score: 1): Author: >; Date: Wed, 10 Dec 2003 13:36:27 -0800; I did try memtest86, but found no problem. I even swapped brand new RAM. Is there more info I can provide? Regards, Norman; /archives/xfs/2003-12/msg00572.html (9,053 bytes)
20. Re: Repair XFS (score: 1): Author: >; Date: Wed, 10 Dec 2003 16:37:20 -0500; fsck.xfs is a no-op. What you need to do is use xfs_repair on the partition while it is unmounted. Note also that anything in lost+found will be "relost" and then "refound" as xfs_repair just unlinks; /archives/xfs/2003-12/msg00573.html (10,099 bytes)

Current List: 1 - 20
Page: [1] [2]