Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Can\'t\s+mount\s+my\s+raid5\s+with\s+2\.4\.7\-pre8\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Can\'t\s+mount\s+my\s+raid5\s+with\s+2\.4\.7\-pre8\s*$/: 15 ]

Total 15 documents matching your query.

1. Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xx>; Date: Fri, 20 Jul 2001 11:48:44 +0200 (MET DST); Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET) After an AC failure, I can't mount my raid5, I get (/users is on fstab: /dev/md0) juno-tty1:~# mount /users Start mounting filesystem: md(9,0) S; /archives/xfs/2001-07/msg00946.html (7,727 bytes)
2. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xx>; Date: Fri, 20 Jul 2001 09:12:47 -0500; This looks very like the log recovery code and the raid code are not playing well with each other - which is a problem. If you actually run repair on the filesystem, it will zero the log and you shou; /archives/xfs/2001-07/msg00962.html (9,078 bytes)
3. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xx>; Date: 20 Jul 2001 10:19:24 -0400; Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we had this problem before they went in. I'll run a few tests here and have a look. -- Martin K. Petersen, Principal Linux Consultant,; /archives/xfs/2001-07/msg00964.html (8,523 bytes)
4. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xx>; Date: Fri, 20 Jul 2001 09:51:34 -0500; This has been reported twice in the last couple of days from the cvs kernel, one was after a clean unmount! Most of the log looks good, but something in there is invalid, xfs_logprint gets confused; /archives/xfs/2001-07/msg00969.html (9,304 bytes)
5. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xx>; Date: 20 Jul 2001 11:07:06 -0400; I just reproduced this in first attempt with a dirty fs on MD RAID5. Looking deeper... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@xxxxxxxxxxxxx, http://www.linuxcare.com/; /archives/xfs/2001-07/msg00972.html (8,721 bytes)
6. Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xxxxxx>; Date: Fri, 20 Jul 2001 11:48:44 +0200 (MET DST); Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET) After an AC failure, I can't mount my raid5, I get (/users is on fstab: /dev/md0) juno-tty1:~# mount /users Start mounting filesystem: md(9,0) S; /archives/xfs/2001-07/msg02237.html (7,727 bytes)
7. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xxxxxx>; Date: Fri, 20 Jul 2001 09:12:47 -0500; This looks very like the log recovery code and the raid code are not playing well with each other - which is a problem. If you actually run repair on the filesystem, it will zero the log and you shou; /archives/xfs/2001-07/msg02253.html (9,078 bytes)
8. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xxxxxx>; Date: 20 Jul 2001 10:19:24 -0400; Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we had this problem before they went in. I'll run a few tests here and have a look. -- Martin K. Petersen, Principal Linux Consultant,; /archives/xfs/2001-07/msg02255.html (8,523 bytes)
9. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xxxxxx>; Date: Fri, 20 Jul 2001 09:51:34 -0500; This has been reported twice in the last couple of days from the cvs kernel, one was after a clean unmount! Most of the log looks good, but something in there is invalid, xfs_logprint gets confused; /archives/xfs/2001-07/msg02260.html (9,304 bytes)
10. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: xxxxxx>; Date: 20 Jul 2001 11:07:06 -0400; I just reproduced this in first attempt with a dirty fs on MD RAID5. Looking deeper... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@xxxxxxxxxxxxx, http://www.linuxcare.com/; /archives/xfs/2001-07/msg02263.html (8,721 bytes)
11. Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: fermin@xxxxxxxxxx (Fermin Molina); Date: Fri, 20 Jul 2001 11:48:44 +0200 (MET DST); Hi, Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET) After an AC failure, I can't mount my raid5, I get (/users is on fstab: /dev/md0) juno-tty1:~# mount /users Start mounting filesystem: md(9,0; /archives/xfs/2001-07/msg03528.html (7,727 bytes)
12. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Fri, 20 Jul 2001 09:12:47 -0500; This looks very like the log recovery code and the raid code are not playing well with each other - which is a problem. If you actually run repair on the filesystem, it will zero the log and you shou; /archives/xfs/2001-07/msg03544.html (9,148 bytes)
13. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Jul 2001 10:19:24 -0400; Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we had this problem before they went in. I'll run a few tests here and have a look. -- Martin K. Petersen, Principal Linux Consultant,; /archives/xfs/2001-07/msg03546.html (8,611 bytes)
14. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Fri, 20 Jul 2001 09:51:34 -0500; This has been reported twice in the last couple of days from the cvs kernel, one was after a clean unmount! Most of the log looks good, but something in there is invalid, xfs_logprint gets confused; /archives/xfs/2001-07/msg03551.html (9,395 bytes)
15. Re: Can't mount my raid5 with 2.4.7-pre8 (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Jul 2001 11:07:06 -0400; I just reproduced this in first attempt with a dirty fs on MD RAID5. Looking deeper... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@xxxxxxxxxxxxx, http://www.linuxcare.com/; /archives/xfs/2001-07/msg03554.html (8,817 bytes)

Current List: 1 - 15
Page: [1]