[lkml]   [2002]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ext3 and undeletion
> another inode after the trunc op would break unix semantics.  In order to
> work, you'd have to use a new inode (in .undelete, of course), copy, then do
> the actual trunc call.
> This would make truncation expensive, whereas before it was pretty fast.
> Modifying unlink will probably suffice.

You would need to hook the truncate/unlink paths in the file system. If
you are doing it within the fs it becomes cheap (at least for ext2) - as
you can simply reassign the data blocks to a new inode, stuff the new inode
into the magic "stuff we deleted" directory and continue.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.103 / U:3.552 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site