https://bugzilla.kernel.org/show_bug.cgi?id=16312 Maciej Rutecki <maciej.rutecki@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |16055 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. --

From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com> You know, do_truncate() can call ext4_setattr() (via notify_change()). And, ext4_setattr() can return with -EFBIG if the argument(length) of do_truncate() is more than sbi->s_bitmap_maxbytes. At that time, it also calls ext4_std_error() with -EFBIG. Besides, a panic happens when ext4_setattr() returns with -EFBIG after we mount an ext4 filesystem with errors=panic. The following steps can make this problem easily. (1) # /bin/dd ...

Yes, right now we are only updating the superblock's lifetime write kbytes at unmount time. It should be possible to do a better job; but I don't want to increase writes to the disk just to keep the s_lifetime value up-to-date. So what we should probably do is update it when we are going to be updating the superblock anyway (i.e., when we update the orphaned inode linked list) and maybe on some periodic basis (say once an hour) otherwise. Thanks for reporting this. I'll put it on my ...