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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+corruption\s+during\s+power\-blackout\s*$/: 78 ]

Total 78 documents matching your query.

1. Re: XFS corruption during power-blackout (score: 1): Author: David Masover <ninja@xxxxxxxxxxxx>; Date: Fri, 01 Jul 2005 03:17:24 -0500; Chris Wedgwood wrote: On Wed, Jun 29, 2005 at 07:53:09AM +0300, Al Boldi wrote: What I found were 4 things in the dest dir: 1. Missing Dirs,Files. That's OK. 2. Files of size 0. That's acceptable. 3.; /archives/xfs/2005-07/msg00000.html (9,389 bytes)
2. Re: XFS corruption during power-blackout (score: 1): Author: Jens Axboe <axboe@xxxxxxx>; Date: Fri, 1 Jul 2005 11:24:14 +0200; And the same (and others) disks will not honor a flush anyways. Moral of that story - avoid bad hardware. -- Jens Axboe; /archives/xfs/2005-07/msg00001.html (9,983 bytes)
3. Re: XFS corruption during power-blackout (score: 1): Author: Ric Wheeler <ric@xxxxxxx>; Date: Fri, 01 Jul 2005 08:36:44 -0400; Chris Wedgwood wrote: On Thu, Jun 30, 2005 at 09:44:37PM +0200, J?rn Engel wrote: Or do you rather mean that a single sync() should block until all data currently present is hardened? Logically sync(; /archives/xfs/2005-07/msg00002.html (12,031 bytes)
4. Re: XFS corruption during power-blackout (score: 1): Author: Ric Wheeler <ric@xxxxxxx>; Date: Fri, 01 Jul 2005 08:53:40 -0400; Bryan Henderson wrote: It's because of the words before that: "everything that was buffered when sync() started is hardened before the next sync() returns." The point is that the second sync() is the; /archives/xfs/2005-07/msg00003.html (12,297 bytes)
5. Re: XFS corruption during power-blackout (score: 1): Author: Jens Axboe <axboe@xxxxxxx>; Date: Fri, 1 Jul 2005 14:56:58 +0200; That is true, sync() really only guarantees that the io has been issued and the drive signalled completion, with write back caching on it might not be on platter yet. -- Jens Axboe; /archives/xfs/2005-07/msg00004.html (12,055 bytes)
6. RE: XFS corruption during power-blackout (score: 1): Author: "Al Boldi" <a1426z@xxxxxxxxx>; Date: Fri, 1 Jul 2005 17:05:11 +0300; And the same (and others) disks will not honor a flush anyways. Moral of that story - avoid bad hardware. } 1. Sync is not the issue. The issue is whether a journaled FS can detect corrupted files an; /archives/xfs/2005-07/msg00005.html (9,974 bytes)
7. Re: XFS corruption during power-blackout (score: 1): Author: Alistair John Strachan <s0348365@xxxxxxxxxxxx>; Date: Fri, 1 Jul 2005 17:35:30 +0100; I agree, I've used XFS for about three years on Linux now, and whilst I love the performance and self-repair attributes of the filesystem, I do think it leaves a lot to be desired when it comes to fi; /archives/xfs/2005-07/msg00006.html (11,346 bytes)
8. Re: XFS corruption during power-blackout (score: 1): Author: Bryan Henderson <hbryan@xxxxxxxxxx>; Date: Fri, 1 Jul 2005 11:24:20 -0700; Hear, hear to all of that. sync() has gotten to be really old-fashioned. You can sync an invidual filesystem image if the filesystem is on a block device or a suitable simulation of one, by opening; /archives/xfs/2005-07/msg00007.html (12,287 bytes)
9. Re: XFS corruption during power-blackout (score: 1): Author: David Masover <ninja@xxxxxxxxxxxx>; Date: Fri, 01 Jul 2005 14:58:39 -0500; What you'd really like is to fsync a multi-file unit of work (transaction) -- and not just among open files. You'd like to open, write, and close 1000 files in a single transaction and then commit th; /archives/xfs/2005-07/msg00008.html (10,528 bytes)
10. Re: XFS corruption during power-blackout (score: 1): Author: Jörn Engel <joern@xxxxxxxxxxxxxxxxxxxx; Date: Fri, 1 Jul 2005 23:10:06 +0200; Both are pretty trivial to implement for a tree-based fs like reiserfs. Non-trivial is the user interface. Not sure if sys_reiser is the answer to that. Jörn -- When people work hard for you for a; /archives/xfs/2005-07/msg00009.html (10,546 bytes)
11. Re: XFS corruption during power-blackout (score: 1): Author: David Masover <ninja@xxxxxxxxxxxx>; Date: Fri, 01 Jul 2005 16:39:25 -0500; Jörn Engel wrote: On Fri, 1 July 2005 14:58:39 -0500, David Masover wrote: Bryan Henderson wrote: [...] What you'd really like is to fsync a multi-file unit of work (transaction) -- and not just am; /archives/xfs/2005-07/msg00010.html (11,353 bytes)
12. Re: XFS corruption during power-blackout (score: 1): Author: Sonny Rao <sonny@xxxxxxxxxxx>; Date: Tue, 5 Jul 2005 11:53:22 -0400; On all the SCSI drives shipped w/ servers write-caching is turned off for this very reason. This is true of all the IBM equipment I've seen, not sure about the smaller mom & pop outfits or drives sol; /archives/xfs/2005-07/msg00021.html (11,535 bytes)
13. Re: XFS corruption during power-blackout (score: 1): Author: Sonny Rao <sonny@xxxxxxxxxxx>; Date: Tue, 5 Jul 2005 11:49:19 -0400; Journaling implies filesystem consistency, not data integrity, AFAIK. Ext3 has stronger guaranties than basic filesystem consistency. I.e. in ordered mode, file data is always written before metadata; /archives/xfs/2005-07/msg00022.html (12,208 bytes)
14. RE: XFS corruption during power-blackout (score: 1): Author: "Al Boldi" <a1426z@xxxxxxxxx>; Date: Tue, 5 Jul 2005 20:25:11 +0300; Sonny Rao wrote: { Ext3 has stronger guaranties than basic filesystem consistency. I.e. in ordered mode, file data is always written before metadata, so the worst that could happen is a growing file'; /archives/xfs/2005-07/msg00023.html (10,319 bytes)
15. Re: XFS corruption during power-blackout (score: 1): Author: Sonny Rao <sonny@xxxxxxxxxxx>; Date: Tue, 5 Jul 2005 14:10:57 -0400; I beleive in newer 2.6 kernels that Reiser has ordered mode (IIRC, courtesy of Chris Mason), but XFS and JFS do not support it. I seem to remember Shaggy (JFS maintainer) saying in older 2.4 kernels; /archives/xfs/2005-07/msg00024.html (12,197 bytes)
16. Re: XFS corruption during power-blackout (score: 1): Author: Dieter Nützel <Dieter.Nuetzel@xxxxxxxxxx; Date: Tue, 5 Jul 2005 21:24:48 +0200; Am Dienstag, 5. Juli 2005 20:10 schrieb Sonny Rao: And SuSE, ack. ftp://ftp.suse.com/pub/people/mason/patches/data-logging They are around some time ;-) Greetings, Dieter -- Dieter Nützel @home: <D; /archives/xfs/2005-07/msg00025.html (12,362 bytes)
17. RE: XFS corruption during power-blackout (score: 1): Author: "Al Boldi" <a1426z@xxxxxxxxx>; Date: Wed, 6 Jul 2005 07:24:03 +0300; Sonny Rao wrote: { I believe in newer 2.6 kernels that Reiser has ordered mode (IIRC, courtesy of Chris Mason), but XFS and JFS do not support it. } Was ordered mode disabled/removed when XFS was add; /archives/xfs/2005-07/msg00027.html (10,949 bytes)
18. Re: XFS corruption during power-blackout (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Wed, 6 Jul 2005 14:46:26 +1000; No, XFS has never supported such a mode. cheers. -- Nathan; /archives/xfs/2005-07/msg00028.html (10,268 bytes)
19. Re: XFS corruption during power-blackout (score: 1): Author: "Russell Howe" <rhowe@xxxxxxxxxxxx>; Date: Wed, 6 Jul 2005 12:27:20 +0100; See the FAQ: http://oss.sgi.com/projects/xfs/faq.html#nulls XFS only journals metadata, not data. So, you are supposed to get a consistent filesystem structure, but your data consistency isn't guaran; /archives/xfs/2005-07/msg00029.html (11,346 bytes)
20. Re: XFS corruption during power-blackout (score: 1): Author: Ethan Benson <erbenson@xxxxxxxxxx>; Date: Wed, 6 Jul 2005 18:56:07 -0800; that was me. note that +S on directories does not make everything in that directory synchronous automatically, you need to apply it recursively. what +S on the directory will do is ensure any new fil; /archives/xfs/2005-07/msg00030.html (11,461 bytes)

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