search for: jdirty

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops in journal_insert_checkpoint() (line 385, &quo...

...ly unused but is defined in jbd.h as BH_Freed, /* 1 if buffer has been freed (truncated) */ It seems perfect for the job. At this point in journal_unmap_buffer, we set BH_Freed on the buffer. Then in phase 7 of the commit, when we are looking at the t_forget buffers and considering if they are jdirty, and hence should be made really dirty again, we avoid doing so if BH_Freed is set. I am yet to actually try this patch out on a production system, partly because I wanted to be sure my understanding was good enough to be able to convincingly explain it in Email first, and partly because it is lat...

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |