From: David Woodhouse <dwmw2@infradead.org>
To: Simon Munton <Simon.Munton@m4data.co.uk>
Cc: "MTD (E-mail)" <mtd@infradead.org>, "JFFS (E-mail)" <jffs-dev@axis.com>
Subject: Re: Problem with deleted files
Date: Fri, 26 Jan 2001 13:53:49 +0000 [thread overview]
Message-ID: <16862.980517229@redhat.com> (raw)
In-Reply-To: <52AF3CB987C7D41183CD0090271F67C301C929@m4eng.m4data.co.uk>
Simon.Munton@m4data.co.uk said:
> This could be fixed by always setting a node's deleted flag if the
> corresponding file's deleted flag is set, when it is written in
> jffs_write_node() and jffs_rewrite_data(). Can anyone see any problems
> with this?
Er... I thought we already did this. Yes, that's what I'd recommend. Once
you're sure it's happy, can you commit the same change to the
linux-2_4-branch too, please?
Simon.Munton@m4data.co.uk said:
> Should the filesystem fail to mount if it finds a node with no parent?
> Would it be better to just throw away such nodes, or perhaps create a
> virtual lost+found directory and put them there?
I'd just let it mark them as deleted. JFFS2 will do that anyway - I'm not
going to bother with marking inodes as deleted. They'll just fade away when
nlink (calculated dynamically from the dirents) gets to zero.
The whole thing gets _so_ much more interesting when you no longer GC in
strict order, and you can GC the 'deletion' nodes before you actually GC
the nodes they're deleting...
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2001-01-26 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 13:38 Problem with deleted files Simon Munton
2001-01-26 13:53 ` David Woodhouse [this message]
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=16862.980517229@redhat.com \
--to=dwmw2@infradead.org \
--cc=Simon.Munton@m4data.co.uk \
--cc=jffs-dev@axis.com \
--cc=mtd@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox