t; /data/lsf Nov 13 14:50:36 lnx0129 automount[948]: attempting to
> mount entry /data/alpha1 Nov 13 14:54:52 lnx0129 kernel: VFS: Busy
> inodes after unmount. Self-destruct in 5+seconds. Have a nice
> day... Nov 13 14:54:52 lnx0129 automount[27090]: expired /data/lsf
> Nov 13 14:59:52 ln
4:52 lnx0129 kernel: VFS: Busy inodes after unmount. Self-destruct in 5
+seconds. Have a nice day...
Nov 13 14:54:52 lnx0129 automount[27090]: expired /data/lsf
Nov 13 14:59:52 lnx0129 automount[27092]: expired /data/alpha1
I was wondering if anyone has ever seen this before? We are using the
RedHa
> After restarting linux this evening, during bootup it complained about
> "/dev/hda2: Deleted inodo 14989 has zero dtime" for about ten different
> inodes. Now, I understand what an inode is, so does this mean that a file
> just got the axe for each of these? Is there any
mply turning off the power or pressing the reset button.
You should always push control-alt-delete or use the 'shutdown' command.
> inodes. Now, I understand what an inode is, so does this mean that a file
> just got the axe for each of these? Is there any means of checking wha
After restarting linux this evening, during bootup it complained about
"/dev/hda2: Deleted inodo 14989 has zero dtime" for about ten different
inodes. Now, I understand what an inode is, so does this mean that a file
just got the axe for each of these? Is there any means of checkin
