search for: chacron

Hi, I have an ext3 file system on top of LVM and i use journaled mode. I would like to make a snapshot of my filesystem while the application is running in order to backup on another physical storage. For that i have to create an LVM snapshot and then to mount it in read-only for copying the content. This is not possible as far as ext3 needs to do a log replay at mount time ( AFAIK). I would

...city or ordering guarantees". I just want to know if, in practical, you have encoutered any problem of data consistency after a failure using ext3 (or another File System with atomic data writting propriety) through NFS and in what precise cases. I'll enjoy to have your feedback. Eric Chacron, Alcatel Software Control Platform

Hi Stephen, I use ext3 with kernel 2.4.14. I'm happy to have verified that nfs+ext3 in journal mode doesn't provide atomic write for the user point of view. My program writes sequential records of 64KB in a file through a nfs mount point. The blocks of data are initialized with a serie of integer: 1, 2, 3 ... I kill the nfsd daemons while two instance of the program are writing their 600

Hi Stephen, I would like to know the behavior of ext3 for a write() request used with O_SYNC for 64 K in term of disk access method: - is there a chance to have only one disk access (instead of 16 x 4 K corresponding to each mapped page ) or at maximum two in journaled mode ? - if this is possible then how can i force such a grouping of data in a single disk output ? NB: i disable cached write

Hi Stephen, "Stephen C. Tweedie" wrote: > Hi, > > On Thu, Jun 20, 2002 at 05:35:45PM +0200, chacron1 wrote: > > > I redo some test with 2.4.14 ext3 and raw device . > > Please try the current ext3, from -ac or ext3 cvs, to make sure you're > not hitting something that's been fixed since 2.4.14. 2.4.14 is a > very old, and known buggy kernel. > I have tried with 2...