similar to: kernel oops

Hi Stephen, I posted a similar report on linux-kernel a month ago, but didn't hear anything new from you. So I try it again in this list, this time with some additional info: Using a stock 2.2.17 kernel with NFS-patches and ext-0.0.3b I can reliably lockup the kjournald when extracting two or three tar.gz files (e.g. kernel tar-balls) onto a ext3 filesystem with activated quotas. This

Hi, Newbie question here. I've read some about how you can't power down a disk under ext3 because of the journaling writes. I also know I can mount my ext3 partitions as ext2. What about mounting the partitions as ext2 while mobile on batteries? The hard disk would spin down when it wasn't in use (if noflush, etc. has been configured). But what about data integrity when

I am running postfix on RH machine. decided to upgrade one of my machines from 7.1 to 7.2 - performance drop of 75 percent !!!!! moved back to ext2(remount partition as ext2) - performance is back. on the 7.1 upgraded to ext3 (only the disks), rebooted - performance drop of 70 percent... used a 2.4.17 kernel compiled by myself - a little faster then the last RH kernel, but still runs at third

The list has gotten pretty quiet over the last week. As I understand it, we are down to the following big ticket items: 1. Quotas on meta journaling 2. ext3 + LFS 3. Various minor bugs. Is this accurate? -- Keith Barrett Red Hat HA Team

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Following the announcement on lkml, I have started using ext3 on one of my servers. Since the server in question is a farily security-sensitive box, my /usr partition is mounted read only except when I remount rw to install packages. I converted this partition to run ext3 with the mount options "nodev,ro,data=writeback,defaults" figuring that when I need to install new packages etc,

There hasn't been any mailing list activity for almost a week. Is it that we are all happy and just waiting for meta-data journaling? -- Keith Barrett Red Hat HA Team

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Dear all, I followed the instructions found on http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html to convert / on several of my boxes to ext3. Strange to me, on some boxes it perfectly worked while on others it didn't. One of the differences found is that on the ok-boxes mount reports: /dev/hda3 on / type ext3 (rw,errors=remount-ro) /* Settings: cat /etc/fstab /dev/hda3 / ext3

Hi, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

All -- I'm curious is if it safe or even wise to run the following command on a mounted filesystem, namely root (/)? tune2fs -j /dev/hda1 What about if someone goes into single user mode and runs this first? mount -o remount,ro / And then to enable it, runs this? mount -t ext2 -o remount,rw / I assume it is not safe to do so, but one user in my LUG assumes otherwise. Just curious,

I have a usb hd that I use for backup. Occasionally it dies. scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): read_inode_bitmap: Cannot read inode bitmap -

Can anyone comment on whether or not it is possible to successfully disable the journal of an ext3 root file system prior to reboot? My application is to try and make sure there is no journal prior to installing and rebooting into a system which does not support ext3. I know that as long as the root is cleanly remounted r/o with no journal updates pending, this will be compatible. I'm

I have a NFS server with stock 2.4.20 patched with the 5 data=journal patches, plus the 2.4 LSM and NSA's selinux. The partition is mounted with the options: rw,noatime,nosuid,nodev,data=journal,errors=remount-ro The oops seems to happen when the fs is under load. I don't think I encountered this behavior with a non LSM/selinux kernel, so it may have something to do with those, but I

In 1.6.0, when creating a MDT, you could specify multiple --mgsnode options and it would failover between them. 1.6.3 only seems to take the last one and --mgsnode=192.168.1.252 at o2ib:192.168.1.253 at o2ib doesn''t seem to failover to the other node. Any ideas how to get around this? Robert Robert LeBlanc College of Life Sciences Computer Support Brigham Young University leblanc at

I had a power-fail this morning, and when I rebooted, /etc/rc.d/rc.boot issued a 'mount -n -o remount,ro /' and then a 'fsck -A -V -a -C'. The fsck failed on my root partition. I know why it failed. It called fsck.ext2 . My root poartition is ext3. My question is, why did it call fsck.ext2? Another question, why was it checked at all? My /etc/fstab contains: /dev/hda1 / ext3

Hi, I installed RH 7.2 with the original kernel and decided to use ext3 as the fs. All partitions are now ext3. This is working fine as long as I'm using the original kernels. Now I wanted to compile my own kernel (2.4.13), but there seems to be a problem. When it it tries to remount my root partition / in RW, I get an error message that the partition cannot be found. When I reboot using the

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778)

Greetings, I recently cpio-ed some user directories onto a new ext3 partion. After putting this file server's partition into production, I noticed a .journal file in the root directory of the partition dated well before the creation of this partition. I think this .journal file was copied over from the old filesystem and I am concerned that I over-wrote this current filesystem's