Hello guys
Analyzing a crash dump I noticed some orphan / suspicious open file descriptors:
crash> fuser /mnt
No users of /mnt
crash> mount -f /dev/sdb1
VFSMOUNT SUPERBLK TYPE DEVNAME DIRNAME
ffff88094c4cc680 ffff880946018c00 myfs /dev/sdb1 /mnt
OPEN FILES
DENTRY INODE TYPE PATH
ffff880936419900 ffff8808d17c5518 REG foo.txt
Does anyone knows how to turn those addresses into something useful?
I already tried some of the commands that looked like could do
something... but no good.
crash> eval ffff880936419900
hexadecimal: ffff880936419900
decimal: 18446612171879192832 (-131901830358784)
octal: 1777774200446620314400
binary: 1111111111111111100010000000100100110110010000011001100100000000
crash> extend ffff880936419900
extend: ffff880936419900: No such device or address
crash> struct ffff8808d17c5518
struct: invalid data structure reference: ffff8808d17c5518
I was hopping to get something like when I type "inode" but with
values in the fields.
I'm just learning to use crash... and I'm not sure if to expect a
struct inode there. Also in the documentation it doesn't specifies
whether "address" means "in memory" or "in disk".
http://www.tldp.org/LDP/tlk/ds/ds.html
http://people.redhat.com/anderson/crash_whitepaper/help_pages/mount.html
Any ideas?
Ismael
--
Do not let me induce you to satisfy my curiosity, from an expectation,
that I shall gratify yours. What I may judge proper to conceal, does
not concern myself alone.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
