A few more things: 1) Does it affect all filesystems (this seems to be implied, but I'm not sure) 2) Does it only affect ext3 filesystems - can you unmount one of them, and mount it up ext2, and see if the problem persists. If so, recreate the ext3 journals. 3) If the answer to 2 is no, does it affect other filesystem types (mount -t tmpfs -o size=32m tmpfs /mnt/tmpfs)? 4) Does it affect newly created filesystems - you can create a ramdisk filesystem like mkfs.ext3 /dev/ram2 ; mount /dev/ram2 /media On Dec 5, 2007 9:12 PM, Jon Stanley <jonstanley@xxxxxxxxx> wrote: > On Dec 5, 2007 8:59 PM, Madan Thapa <madan.feedback@xxxxxxxxx> wrote: > > Gary, > > > > A kernel upgrade fixed the issue for a while but I ended up with an OS > > reload. > > Kernel upgrade seems odd. This came up once before in #rhel on > freenode, and we were all stumped. I believe the user in that case > was running the latest kernel, had no aliases, etc to rule out all the > "usual suspects". Sounds like some type of weird filesystem > corruption. Have you tried to force fsck on the filesystem? > > I am *really* interested in what this ends up being, if it's ever found out. > > -Jon > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
