Re: Dtime of Inodes
On Sun, Jul 26, 1998 at 07:43:29PM +1000, Hamish Moffatt wrote:
> On Sat, Jul 25, 1998 at 07:10:03PM -0700, Alexander wrote:
> > A deleted inode seems to have zero dtime sometimes when the machine is not
> > shut down normally. (i.e., power failure, system crash, nuclear
> > accident...)
> I tend to get them when the check is forced (due to 30 unchecked mounts),
> without any abnormal shutdowns. I don't know why.
This was posted to the kernel mailing list recently, I havn't checked
Debian's status on this yet:
In article <firstname.lastname@example.org>, <email@example.com> wrote:
>Oh well. I asked because the line "Deleted inode 10413 has zero dtime."
>always indicated a dynamic init for me.
That happens when you upgarde your libraries and remove the old libs-
init is still using them, so after a reboot you do indeed get a
"has zero dtime" warning.
Since sysvinit-2.74 you can use "telinit u" to "upgrade" init. Init
will reload itself from /sbin/init and preservce all state. That's
great after a library upgrade. Kudos to Alexander Viro.
Miquel van Smoorenburg | Our vision is to speed up time,
firstname.lastname@example.org | eventually eliminating it.
email: email@example.com, http://www.poboxes.com/adrian.bridgett
Windows NT - Unix in beta-testing. PGP key available on public key servers
Debian Linux http://www.debian.org The superior Linux distribution
Unsubscribe? mail -s unsubscribe firstname.lastname@example.org < /dev/null