Messages in this thread | | | Date | Sun, 26 Jan 2003 12:25:50 +0300 | From | Oleg Drokin <> | Subject | Re: ext2 FS corruption with 2.5.59. |
| |
Hello!
On Sat, Jan 25, 2003 at 03:13:01PM -0800, Andrew Morton wrote: > > Also I think that taking BKL just to update some inode accounting stuff is kind of expensive, > > so certainly better solution must exist. > However, in reviewing it, I don't see exactly what's going on. Because only > one process is accessing the stat information of the fsx inode anyway?
Well, I came to conclusion that we have fsx doing truncate racing with fsstress doing sync->iput->ext2_discard_prealloc()
> Yes, we need to rub out that i_bytes/i_blocks thing, replace it with an > atomically updated loff_t, etc. But I'd like to understand what the exact > failure is first. It _seems_ that stat has somehow seen a >4G value of > stat->size, but how can this happen???
It's just become negative as we discarding prealloc twice.
Bye, Oleg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |