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

Results:

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

Total 16 documents matching your query.

1. XFS filesystem shutdown (score: 1): Author: Mike Brodbelt <m.brodbelt@xxxxxxxxx>; Date: Tue, 09 Dec 2003 15:42:59 +0000; I've been using XFS on numerous systems for about 2 years now, and I've recently been bitten by a problem I've seen once or twice before, and was wondering if anyone out there knows what the real cau; /archives/xfs/2003-12/msg00144.html (9,060 bytes)
2. Re: XFS filesystem shutdown (score: 1): Author: "Simon Matter" <simon.matter@xxxxxxxxxxxxxxxx>; Date: Wed, 10 Dec 2003 08:22:50 +0100 (CET); I've been running cyrus-imapd servers on XFS for years now without any problems related to XFS. I also had the sig11 and die problem but it never affected XFS, and I think it really should not. ^^^^; /archives/xfs/2003-12/msg00157.html (10,908 bytes)
3. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 10:28:42 +0000; I agree - a non root userland process should definitely not affect the filesystem. I mentioned it only because it may be a reason for a non-expected pattern of fs operations. That was the dmesg outpu; /archives/xfs/2003-12/msg00162.html (9,456 bytes)
4. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 10:44:22 +0000; There are a couple of retries on one of the disks, but nothing that I think should have "show through" to the OS. I suppose I can't discount the possibility entirely, as the error came up about 4 day; /archives/xfs/2003-12/msg00163.html (9,773 bytes)
5. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 10:17:52 -0600; What enclosures are you using for your drives? We had a ICP vortex card with CI-design enclosures we bought that we're supposed to be ultra-160. As it tuns out when we opened the CI-design enclosures; /archives/xfs/2003-12/msg00173.html (11,364 bytes)
6. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 16:33:38 +0000; I have had enclosure problems on that machine in the past. I have U160 drives, but I've got the sync rate set down to 80, as I was getting an unacceptably high level of retries, and I had disks repor; /archives/xfs/2003-12/msg00175.html (9,975 bytes)
7. Re: XFS filesystem shutdown (score: 1): Author:; Date: 10 Dec 2003 15:15:03 -0600; I'm always happy to blame hardware, believe me. :) But error 22 is "EINVAL" on x86, so I suppose it's possible that xfs did something wrong like request a block off the end of the device, and the dri; /archives/xfs/2003-12/msg00189.html (8,881 bytes)
8. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 11:36:09 +0100; Mike Brodbelt wrote: I'm not an expert for those error messages but I guess it unfortunately a hardware error, isn't it? Did you check dmesg output when this happened? That was the dmesg output - no; /archives/xfs/2003-12/msg00247.html (9,407 bytes)
9. XFS filesystem shutdown (score: 1): Author:; Date: Tue, 09 Dec 2003 15:42:59 +0000; I've been using XFS on numerous systems for about 2 years now, and I've recently been bitten by a problem I've seen once or twice before, and was wondering if anyone out there knows what the real cau; /archives/xfs/2003-12/msg00525.html (9,060 bytes)
10. Re: XFS filesystem shutdown (score: 1): Author:; Date: Wed, 10 Dec 2003 08:22:50 +0100 (CET); I've been running cyrus-imapd servers on XFS for years now without any problems related to XFS. I also had the sig11 and die problem but it never affected XFS, and I think it really should not. ^^^^; /archives/xfs/2003-12/msg00538.html (10,908 bytes)
11. Re: XFS filesystem shutdown (score: 1): Author: x; Date: Wed, 10 Dec 2003 10:28:42 +0000; I agree - a non root userland process should definitely not affect the filesystem. I mentioned it only because it may be a reason for a non-expected pattern of fs operations. That was the dmesg outpu; /archives/xfs/2003-12/msg00543.html (9,456 bytes)
12. Re: XFS filesystem shutdown (score: 1): Author: >; Date: Wed, 10 Dec 2003 10:44:22 +0000; There are a couple of retries on one of the disks, but nothing that I think should have "show through" to the OS. I suppose I can't discount the possibility entirely, as the error came up about 4 day; /archives/xfs/2003-12/msg00544.html (9,773 bytes)
13. Re: XFS filesystem shutdown (score: 1): Author: >; Date: Wed, 10 Dec 2003 10:17:52 -0600; What enclosures are you using for your drives? We had a ICP vortex card with CI-design enclosures we bought that we're supposed to be ultra-160. As it tuns out when we opened the CI-design enclosures; /archives/xfs/2003-12/msg00554.html (11,364 bytes)
14. Re: XFS filesystem shutdown (score: 1): Author: >; Date: Wed, 10 Dec 2003 16:33:38 +0000; I have had enclosure problems on that machine in the past. I have U160 drives, but I've got the sync rate set down to 80, as I was getting an unacceptably high level of retries, and I had disks repor; /archives/xfs/2003-12/msg00556.html (9,975 bytes)
15. Re: XFS filesystem shutdown (score: 1): Author: >; Date: 10 Dec 2003 15:15:03 -0600; I'm always happy to blame hardware, believe me. :) But error 22 is "EINVAL" on x86, so I suppose it's possible that xfs did something wrong like request a block off the end of the device, and the dri; /archives/xfs/2003-12/msg00570.html (8,881 bytes)
16. Re: XFS filesystem shutdown (score: 1): Author: >; Date: Wed, 10 Dec 2003 11:36:09 +0100; Mike Brodbelt wrote: I'm not an expert for those error messages but I guess it unfortunately a hardware error, isn't it? Did you check dmesg output when this happened? That was the dmesg output - no; /archives/xfs/2003-12/msg00628.html (9,407 bytes)

Current List: 1 - 16
Page: [1]