GNU bug report logs - #24406
rm command: different behaviors seen with indirect blocks of a file

Previous Next

Package: coreutils;

Reported by: "Kothagere Siddalinga, Mahesh" <mxk145330 <at> utdallas.edu>

Date: Sat, 10 Sep 2016 17:59:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: "Kothagere Siddalinga, Mahesh" <mxk145330 <at> utdallas.edu>
To: 24406 <at> debbugs.gnu.org
Subject: bug#24406: rm command: different behaviors seen with indirect blocks of a file
Date: Sat, 10 Sep 2016 16:51:49 +0000

[Message part 1 (text/plain, inline)]
Hi,

I am Mahesh, part of the team that is working on a tool to undelete the files on ext3 file system.
One of the ideas on which the tool is based is “the rm command marks the inode free but does not zero out the data blocks and the indirect blocks”
While this is validated to be true on my version of Linux, Ubuntu 16.04, some of my friends using fedora found out that the indirect blocks at the 13th pointer of the inode is indeed being zeroed.

This difference of behavior is seemingly mysterious to me. Request you to point me in the direction as to why only some distributions of Linux seems to zero out the indirect block pointers associated with the files.

Thanks,
Mahesh.

[Message part 2 (text/html, inline)]
This bug report was last modified 8 years and 259 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.