On Wed, Aug 25, 2010 at 02:25:37PM -0700, Vitali Lovich wrote: > > For a long-term fix, it probably would make sense to patch ext3/ext4 > > so that when we delete a file, and the current time is less than > > number of inodes, that we set dtime to 0xffffffff. > > Is the i_dtime actually used at all? Could we just patch it to always > set that as the i_dtime always? I grepped the source, & no one is > actually using the i_dtime field. It's not used by the kernel, but it is used occasionally by people who are trouble shooting file systems, and want to know when a particular inode was deleted. So a local hack to always set i_dtime to ~0 would not be horrible. But something which sets i_dtime to the system time, unless this would cause confusion with an orphaned inode linked list, in which case ~0 is used instead, is probably a cleaner fix. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
