Re: viewing inode data


"Scott Lurndal" <scott@xxxxxxxxxxxxx> wrote in message
news:49daacd0$0$19072$f56e502@xxxxxxxxxxxxxxxxxxxxxxxx

What do you think is in 'buffer'?

(Hint: It's the inode data).

Type 'man 2 stat'

Ok I see. :) I use the linux command shred from time to time. I am using
an ext3 filesystem. Is there a way I can name the inode number for example,
using ls -lai in a directory, and read its' inode numbers for files. What
I'm really getting at here is using shred or redirecting /dev/random or
/dev/zero to an area in the filesystem really erasing all trace of the file?
I think the files can be recreated by using inode data. I may be wrong but
could using shred hold up againsts a DoD or forensic analysis attempt. And
let me say here I am not keeping anything illegal on my HD too.

Bill


.

Relevant Pages

  • Unable to remove broken ext3 journal
    ... The journal on my ext3 filesystem is corrupted, ... The symptom is that running e2fsck claims that it finds numerous ... Inode 8 has illegal block. ... Illegal block number passed to ext2fs_unmark_block_bitmap ...
    (comp.os.linux.misc)
  • Re: viewing inode data
    ... The way I understand it when a file using the ext3 filesystem is ... Information from the file can be extracted from the inode even if shred ... Would that envolve creating a pipe? ... Now stop smoking, will you? ...
    (comp.unix.programmer)
  • Re: max number of file in a fs
    ... > is there a maximun numer of files on a ext3 filesystem? ... supreblock info for the file system system. ... Inode blocks per group: 251 ... There is a limit on the number of inodes on a file system indicated by ...
    (linux.redhat)
  • Re: ARC-1260: No space left on device, when there is (or should be) free space left
    ... MN> Inode count: 1430528 ... I created an 8TB partition here and made an ... ext3 filesystem in it with the default parameters; ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Deleting a file with a damaged filename
    ... linux 3.1.0-1.2-desktop x86_64 ... stat: cannot stat `versi\377': No such file or directory ... However, it may be that inode numbers are pointing to unallocated inodes, so first try to umount that partition and do as root fsck -f ...
    (comp.os.linux.misc)