similar to: NFS/InterMezzo ext3 problem

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 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 -

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

Hello ext3-users, we have an oopsy situation here: we have 4 machines: 3 client nodes, 1 master: the master holds a fairly big repository of small files. The repo's current size is ~40GB with ~1.2 M files in ~100 directories. Now, we like to rsync changes from the master to the client nodes, which is working perfectly for 2 nodes, but our 3rd node oopses "sometimes", rendering

hello! i'm using redhat 7.2 with ext3 as my primary fs on kernel 2.4.17 + grsecurity + acl after 2-3 days of uptime i'm expiriencing problems... i attached below excert from my system logs. machine stops responing for a few seconds and after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle... after

hello! i'm using redhat 7.2 with ext3 as my primary fs on kernel 2.4.17 + grsecurity + acl after 2-3 days of uptime i'm expiriencing problems... i attached below excert from my system logs. machine stops responing for a few seconds and after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle...

Hi, I got the OOPS below on my laptop running vanilla 2.4.20-ac2; I had to copy it byhand so it may not be 100% accurate. It hasn't happened again, and this is the first problem I've had with this kernel (or any other kernel, for that matter.) Anyway, I'm not sure, if a) this is actually an ext3 problem, b) OOPS reports of 2.4.20-ac2 are of any interest, so I won't bother with

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

Today our server had seriuos problems, we had to reinitiate it and run fsck manually. Dou you think it's an ext3, kernel (vanilla 2.4.19) or hardware bug? The errors were (from syslog): -------------------------------- Oct 6 16:10:25 nou kernel: attempt to access beyond end of device Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=230266240, limit=4882432 Oct 6 16:10:25 nou kernel: attempt

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

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:

btrfs_ilookup is unused, which is good because a normal filesystem should never have to use ilookup anyway. Remove it. Signed-off-by: Christoph Hellwig <hch@lst.de> Index: btrfs-unstable/ctree.h =================================================================== --- btrfs-unstable.orig/ctree.h 2008-08-30 11:08:58.000000000 -0300 +++ btrfs-unstable/ctree.h 2008-08-30 11:09:10.000000000

Hi, I have a detailed question about ordered data writes. Suppose we (i.e. intermezzo) does a transaction, which is closed and then followed by an ordered write. Let's assume the ordered write doesn't require new allocation metadata. Is the write still postponed until the first transaction has committed? As far as I can see, prepare_write always starts a transaction, but I'm

Kill warning if CONFIG_QUOTA is disabled. --- linux-2.4.23/fs/ext3/super.c.orig Fri Nov 28 21:04:40 2003 +++ linux-2.4.23/fs/ext3/super.c Sun Nov 30 12:16:00 2003 @@ -449,7 +449,6 @@ } static struct dquot_operations ext3_qops; -static int (*old_sync_dquot)(struct dquot *dquot); static struct super_operations ext3_sops = { read_inode: ext3_read_inode, /* BKL held */ @@ -1773,6 +1772,8 @@

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

One of our servers (false) just oopsed. In the middle of lunch. Any advise? On console: false kernel: Assertion failure in journal_start() at transaction.c line 245: "handle->h_transaction->t_journal == journal" In kernel log (ran it through ksymoops): Nov 13 12:35:37 false kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Nov 13 12:35:37

-----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

On a 2.4.17 (MontaVista 2.1) kernel using ext3, I recently starting seeing the error EXT3-fs error (device ide1(22,1)) in start_transaction: Readonly filesystem EXT3-fs error (device ide1(22,1)) in ext3_delete_inode: Readonly filesystem on a file system within 10-20 seconds after remounting it r/o. Apparemtly a write is being deferred past the remount point and then runs into problems when it is