Displaying 5 results from an estimated 5 matches for "ext3_force_commit".
2002 Dec 01
3
data corrupting bug in 2.4.20 ext3, data=journal
...nc.c~ext3-fsync-fix Sat Nov 30 23:37:33 2002
+++ linux-akpm-akpm/fs/ext3/fsync.c Sat Nov 30 23:39:30 2002
@@ -63,10 +63,12 @@ int ext3_sync_file(struct file * file, s
*/
ret = fsync_inode_buffers(inode);
- /* In writeback mode, we need to force out data buffers too. In
- * the other modes, ext3_force_commit takes care of forcing out
- * just the right data blocks. */
- if (test_opt(inode->i_sb, DATA_FLAGS) == EXT3_MOUNT_WRITEBACK_DATA)
+ /*
+ * If the inode is under ordered-data writeback it is not necessary to
+ * sync its data buffers here - commit will do that, with potentially
+ * better IO...
2003 Oct 27
2
EXT3 deadlock in 2.4.22 and 2.4.23-pre7 - quota related?
...tate is T_LOCKED, so presumably those nfsd threads above are
waiting on kjournald. But what is kjournald really waiting for?
My first though was the two nfsd threads in:
nfsd Call Trace: [sleep_on+75/124]
[log_wait_commit+74/136] [journal_stop+408/432]
[journal_force_commit+78/128] [ext3_force_commit+66/112]
[ext3_sync_file+128/144] [nfsd_sync_dir+49/72]
[nfsd_unlink+455/480] [nfsd_proc_remove+122/140]
[nfsd_dispatch+207/406] [svc_process+655/1264]
[nfsd+566/944] [arch_kernel_thread+40/56]
that are waiting on j_wait_done_commit. However they are doing that
from journal_stop *afte...
2005 Jan 04
0
[PATCH] BUG on error handlings in Ext3 under I/O failure condition
...--- linux-2.4.29-pre3-bk2/fs/ext3/fsync.c 2002-11-29 08:53:15.000000000 +0900
+++ linux-2.4.29-pre3-bk2_fix/fs/ext3/fsync.c 2005-01-04 19:58:32.000000000 +0900
@@ -69,7 +69,7 @@
if (test_opt(inode->i_sb, DATA_FLAGS) == EXT3_MOUNT_WRITEBACK_DATA)
ret |= fsync_inode_data_buffers(inode);
- ext3_force_commit(inode->i_sb);
+ ret |= ext3_force_commit(inode->i_sb);
return ret;
}
diff -Nru linux-2.4.29-pre3-bk2/fs/ext3/super.c
linux-2.4.29-pre3-bk2_fix/fs/ext3/super.c
--- linux-2.4.29-pre3-bk2/fs/ext3/super.c 2004-11-17 20:54:21.000000000 +0900
+++ linux-2.4.29-pre3-bk2_fix/fs/ext3/super.c 200...
2002 Dec 15
2
problem with Andrew's patch ext3
Hello Andrew,
I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/
and I have a big problem with:
once server is booted on 2.4.20 with your patch, when I want to reboot
with /sbin/reboot, server makes a Segmentation fault and it crashs.
I tested it on 50-60 servers and it is the same problem. I tested kernel
2.4.20 without your patch: no problem.
# uname -a
Linux XXXXXX
2002 Dec 06
2
[patch] fix the ext3 data=journal unmount bug
..._super, /* BKL held */
write_super: ext3_write_super, /* BKL held */
+ sync_fs: ext3_sync_fs,
write_super_lockfs: ext3_write_super_lockfs, /* BKL not held. Take it */
unlockfs: ext3_unlockfs, /* BKL not held. We take it */
statfs: ext3_statfs, /* BKL held */
@@ -1577,24 +1580,22 @@ int ext3_force_commit(struct super_block
* This implicitly triggers the writebehind on sync().
*/
-static int do_sync_supers = 0;
-MODULE_PARM(do_sync_supers, "i");
-MODULE_PARM_DESC(do_sync_supers, "Write superblocks synchronously");
-
void ext3_write_super (struct super_block * sb)
{
+ if (...