search for: fsync_devic

Rebooting to try 2.4.7-ac4, I had Xfree86 crash on exit and hang the machine (it does that once a month or so; this notebook gets booted quite often). After fscking the root and another ext2 partition, the system got to the big ext3 partition and just went dead. No message, no disk activity, no keyboard response. I powered down and rebooted 2.4.7-ac3 patched with ext3-2.4-0.9.5-247ac3, and that

I think I have this one solved, I hope. I think what Andreas and I are running into are a few different assertions. One being the LVM lvm_do_pv_flush caused assertion which is related directly to invalidate_buffers() being called which then triggers refile_buffer() on a journaled buffer, which appears clean in all other ways according to the checks in refile_buffer(). The following is what

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Chris Mason wrote: > > > Hi guys, > > Here's a new patch against 2.4.8-pre8, updated to Al's new super > handling. The differences between the original are small, > but they are big enough that I want extra testing from the > LVM guys (and ext3/XFS). ext3 will probably lock up on unmount with 2.4.8-pre8. The fix is to replace fsync_dev with fsync_no_super in

> ext3 will probably lock up on unmount with 2.4.8-pre8. The fix is > to replace fsync_dev with fsync_no_super in fs/ext3/super.c and > fs/jbd/recovery.c. I'll be generating a new patchset this weekend. Actually if you dont fix recovery.c it will hang the machine when you mount an fs that needs recovering. With the old patches at least umount of ext3 seems fine as is. Alan

Patch against linux-2.4.8 is at http://www.uow.edu.au/~andrewm/linux/ext3/ The only changes here are merging up to 2.4.8 and the bigendian fix. linux-2.4.8-ac1 currently has ext3-0.9.3 which has no known crash-worthy bugs, but is old. I'm about to send Alan a diff which takes -ac up to 0.9.6. The changes between 0.9.3 and 0.9.6 may be summarised as: - Simplify the handling of

This patch fixes the data loss which can occur when unmounting a data=journal ext3 filesystem. The core problem is that the VFS doesn't tell the filesystem enough about what is happening. ext3 _needs_ to know the difference between regular memory-cleansing writeback and sync-for-data-integrity purposes. (These two operations are really quite distinct, and the kernel has got it wrong for

When I copy a file(13Megs) from /home/ to /tmp/, sync takes almost 2 minutes. When I copy the same file to /usr/local/, sync returns almost right away. Both filesystems are ext3 and are on the same harddrive. When sync is running, the harddrive light stays on but I don't hear it doing anything. dmesg doesn't show any errors either. Below is the `time` output for each command. If you