similar to: crashing with ext3

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

[ Tried to check the archives but the website seems to be down or something ] On one of our installations, I am seeing messages such as: EXT3-fs warning (device ide0(3,9))): ext3_free_inode: bit already clearned for inode 14 Anybody know exactly what they mean? These would be on a 0.0.6a system. b.

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

Hi, I have a server configured as follows: a standard 2.4.18 kernel, IDE discs, 1Gb RAM (not all used), load avg around 1-2. a large partition, formatted reiserfs within large partition are 80 300Mb loopback file systems, formatted ext3. I got the following assertion yesterday which forced a lot of processes into D state. I'm not sure how easy it is to reproduce this problem.

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, Doing the following I can generate an assertion in ext3 0.0.7a. I have an ext3 filesystem on /foo. I export /foo via nfs. I then mount via localhost:/foo onto /mnt. Start up a dd to generate a file on the nfs mount. (cd /mnt; dd if=/dev/zero of=./dd.out bs=1024k), then on the localhost filesystem /foo I rm the file. rm -f /foo/dd.out. This results in "ext3_free_inode: bit already

Hello, the following patch series implements quotas for OCFS2. The patch series is based on: git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git linux-next I've adressed Joel's comments, also node recovery is now fully working and I've fixed a few issues I found during my testing. So I'm currently not aware of any bugs. Please review, test, comment. Thanks.

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:

Hello all, I've become confused by the output produced by a call to anova(model1,model2). First a brief background. My model used to predict final tree height is summarised here: Df Sum Sq Mean Sq F value Pr(>F) Treatment 2 748.35 374.17 21.3096 7.123e-06 *** HeightInitial 1 0.31 0.31 0.0178 0.89519

Hi all, I have lots of samba servers and want them to all authenticate against a single password file which will be a LDAP database. Where I want to be: Login to a domain called "FROST" that passes the username:passwd to a domain called "ACR" which checks LDAP. Where I'm at: I can login (from a W2K machine) to a test server called LIBIT which uses LDAP

Hello. I've tried to implement dovecot's deliver LDA to my home mailserver. I've run into troubles :) dovecot-deliver.conf: -- snip -- mail = maildir:%h/Maildir:INBOX=maildir:%h/Maildir mbox_read_locks = flock mbox_write_locks = flock -- snip -- when i run: deliver -d bfg < email.txt dovecot delivers message to ~/Maildir/maildir/new It acctually creates "maildir"

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

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

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

Hello, the following series of patches fixes some issues with OCFS2 quotas. The first patch modifies VFS quota locking, the next patch uses the fact to simplify OCFS2 quota locking and solves a few deadlock issues. The third and the fourth patches fix another possible deadlocks in OCFS2 quota code and the last patch is a minor cleanup. Honza

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

Hi, Apologies, this is going to be quite long - I'm going to provide as much info as possible. I'm running a system with ext3 fs on software RAID. The RAID set-up is as shown below: jlm@nijinsky:~$ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid5] read_ahead 1024 sectors md0 : active raid1 hdc1[1] hda1[0] 96256 blocks [2/2] [UU] md5 : active raid1 hdk1[1] hde1[0]

Hello All, Would like to be able to convert a matrix to a dataframe without losing an assigned dimname. Here is an example that should illustrate what I'm talking about. tableData <- state.x77[c(7, 38, 20, 46), c(7, 1, 8)] names(dimnames(tableData)) <- c("State", "") tableData State Frost Population Area Connecticut 139 3100 4862