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 ten
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
er" <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
> Subject: Re: Dtime of Inodes
> Resent-Date: 20 Jul 1998 17:11:57 -
> Resent-From: debian-user@lists.debian.org
> Resent-cc: recipient list not shown: ;
>
> On Mon, Jul 20, 1998 at 08:16:57AM -0600, [EMAI
Hi...
I think it's a data field in the inode that shows what time the inode was
deleted. If it's zero then it's obviously wrong. (this is mostly just a
guess though, take the word of some ext2fs expert)
Alex
On Mon, 20 Jul 1998 [EMAIL PROTECTED] wrote:
> Date: Mon, 20 Jul 1998 08:16:57 -0600
>
On Mon, Jul 20, 1998 at 08:16:57AM -0600, [EMAIL PROTECTED] wrote:
> Hi All,
>
> I got hamm installed on my system. Everytime el2fsck runs, I get the message
> 'Deleted inode 1234 has a dtime of zero. Fix '
>
> Why does this message come?
well...
you don't want to run e2fsck on a mounted files
5 matches
Mail list logo
