similar to: ordered data

Hi Stephen, We had some starvation/locks happening to us under very heavy load in two cases: - InterMezzo asked ext3 to do a journaled file write (for 1 block) essentially using ext3_write - similarly for truncate. These lockups went away when we started the transaction in InterMezzo and reserved somewhat more space than ext3 does. Any clues as to what this might be? Are the ext3

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |

Hi, First, I want to say that I have fallen in love with CentOS4. I have been using RedHat since the 5.x days. After RedHat dropped the stable system to go to a unstable system and a Enterprise system I felt like I was being left out in the cold. I quickly found out about WhiteBox and used it for quite a while. Then I learned about CentOS...and switched to it for my server needs. I have

An ext3 update for Alan's latest kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The version of ext3 in -ac kernels currently stands at 0.9.6, so this is a fairly large diff. However most of this code has had a decent amount of external testing via the 0.9.9 patch. The changelog since 0.9.6 is below. Please test it if you can, and all being well we shall ask Alan to merge it a

Hi, I noticed that using a sparse file as a loop device leads to non journaled block allocation in Ext3. Is this something that should be fixed? - Peter -

hi, is this rpms differ from redhat's rawhide 2.4.5 kernel which seems to contain ext3. so my question that your rpm contain different ext3 than rh's rpm? or I can simple use rh's rawhide rpms? thanks. yours. ps. please reply to my private address to since I'm not on the list. thanks. > Hi, > > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.

Hi, While doing some stress testing with presto module from the intermezzo project layered over ext3, I got the following assertion failure: Jan 17 23:09:55 planck kernel: Assertion failure in jfs_prelock_buffer_check() at journal.c line 410: "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO || bh->b_jlist == BJ_Data" Jan 17 23:09:55 planck kernel:

Hi, I've looked at how OCFS2 call jbd2_journal_begin_ordered_truncate() (because I've been adding some comments about how is should be used) and noticed that OCFS2 has a potential race in truncate vs transaction commit leading to stale data in file. In particular: There is a race if someone writes new data and we start committing the transaction after

Hi, I've been wondering exactly what you gain by using journaled mode over ordered mode. Are there any known cases where journaled mode could recover where ordered mode wouldn't? Mike

Lo, Actualy i'm looking for documents about journalised file system, in order to be able to compare them self. I need accurate information if i want to make a good study. Thoses informations have to permit me to get answer about table like this : Features \ fs | xfs | ext3 | jfs | reiserfs | ------------------------------------------------- chattr | ? | Y | ? | ?

Given that the default journaling mode of ext3 (i.e. ordered), does not guarantee write ordering after a crash, is this journaling mode safe enough to use for a database such as Oracle? If so, how are out of sync writes delt with? Kind regards, Herta Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Sorry for this general question, but I'd like to hear your opinion on this subject, but I'd like to set up a really working backup solution for my PDC, currently it uses NFS, so there are lots of issues: No ACLs, When NFS server goes down, everything fails. What method would you recommend for replicating folders, keeping existing ACLs

I am the author of BackupPC (http://backuppc.sourceforge.net) and I am working on adding rsync support to BackupPC. I am implementing the server-side in perl, and the client will run vanilla rsync. (BTW, is there the protocol documented? I've answered all my questions by looking at the source, but it would be great to check against any docs.) I started with librsync 0.9.3 and the

I've lurked on this list for a long time, and have learned many details on installing and using Ext3. Thanks! I'm finally posting to solicit feedback on my recently-published book on "Linux Filesystems". This book discusses the use, theory, and installation/integration of journaling and distributed filesystems on Linux, and also discusses what I call 'filesystem adapters'

Hi Alan, Would you be opposed to including an InterMezzo patch for the ac series soon? It doesn't touch anything outside of its fs directory. It would probably help us get a few more users and fits nicely with ext3 being in ac now. We are also quite far along Reiser support for InterMezzo. Please let me know your thoughts on this. Thanks! - Peter -

Even though we allocate more, we should be updating inode i_size as per the arguments passed Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- Changes from V1: We should update i_size only if actual_len and cur_offset are both larger than i_size. Otherwise if actual_len is < i_size and cur_offset > i_size we may end up setting wrong i_size value

Hi, I'm running 0.03b and it appears that after a clean unmount the needs_recovery flag is still set. [This makes is quite cumbersome to switch between ext2 and ext3.] How can this be fixed? Oh, and I'm very happy. - Peter -

During CoW, actually all the pages after i_size contains garbage data, so don't read and duplicate them. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/refcounttree.c | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/refcounttree.c b/fs/ocfs2/refcounttree.c index 1cf9cda..e082623 100644 --- a/fs/ocfs2/refcounttree.c +++

Hi, We have encountered another funny with ext3 on 2.4. Like the kernel NFS server, we have a routine in InterMezzo that does something like looking up an inode by inode number. (compare intermezzo's presto_ilookup or knfsd's nfsfh_iget) Effectively both of these routines do ilookup() { inode = iget(sb, ino) if (inode->i_nlink==0) iput(inode); .... } We find that