From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuelkrause@netscape.net>
Cc: Chris Mason <mason@suse.com>, reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: BTW: 2.4.19-patches-to-come?
Date: Fri, 17 May 2002 08:56:11 +0400 [thread overview]
Message-ID: <20020517085611.A6833@namesys.com> (raw)
In-Reply-To: <3CE46192.7080101@netscape.net>
Hello!
On Fri, May 17, 2002 at 03:49:06AM +0200, Manuel Krause wrote:
> I was curious and I stay curious, as I don't see any program deleting 3
> files just before every crash... (I don't have sizes, places and names...)
It is not necessarily happened to files direectly to a crash.
Any open file, that was deleted, cannot be deleted until it is closed.
e.g. if you'd do "sleep 1000000 </path/somefile ; rm /path/somefile",
/path/somefile won't be deleted until sleep finishes.
If system crash occured and there were still some open, but deleted files,
these files gets removed as part of recovery from crash process.
And it is not possible to find file's names/paths because corresponding
directory entries were already deleted.
BTW it is absolutely the same thing happens with ext2, once you see
e2fsck complains about "DTIME is zero", it deletes
not-yet-deleted-but-scheduled-for-deletion files.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-17 4:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:15 BTW: 2.4.19-patches-to-come? Manuel Krause
2002-05-07 5:22 ` Oleg Drokin
2002-05-07 14:02 ` Yury Yu. Rupasov
2002-05-07 19:35 ` Manuel Krause
2002-05-08 5:30 ` Oleg Drokin
2002-05-08 13:04 ` Chris Mason
2002-05-08 13:08 ` Oleg Drokin
2002-05-08 13:16 ` Chris Mason
2002-05-08 13:20 ` Oleg Drokin
2002-05-08 13:34 ` Chris Mason
2002-05-17 1:49 ` Manuel Krause
2002-05-17 4:56 ` Oleg Drokin [this message]
2002-05-17 9:47 ` Pierre Etchemaite
2002-05-17 9:47 ` Oleg Drokin
2002-05-07 13:52 ` Yury Yu. Rupasov
2002-05-07 20:41 ` Manuel Krause
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 15:36 Dieter Nützel
2002-05-17 15:47 ` Chris Mason
2002-05-17 18:20 ` Dieter Nützel
2002-05-17 18:26 ` Dieter Nützel
2002-05-17 15:54 ` Oleg Drokin
2002-05-17 17:05 ` Dieter Nützel
2002-05-17 18:28 ` Oleg Drokin
2002-05-17 19:44 ` Dieter Nützel
2002-05-18 5:44 ` Oleg Drokin
2002-05-18 13:18 ` Dieter Nützel
2002-05-18 16:29 ` Oleg Drokin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020517085611.A6833@namesys.com \
--to=green@namesys.com \
--cc=manuelkrause@netscape.net \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.