public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Chris AtLee <catlee@canada.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Problems unlinking files
Date: Wed, 11 Sep 2002 14:42:21 +0100	[thread overview]
Message-ID: <27421.1031751741@redhat.com> (raw)
In-Reply-To: <1024499619.9366.25.camel@geb>

On Wed, 19 June 2002, catlee@canada.com said:
> I've noticed some problems with unlinking files with JFFS2 in my linux
> 2.2.18 port.  After unlinking a file, it doesn't appear in the
> directory listing, but if I do an 'ls' on the unlinked file, I can
> still get information on the file.  I can still read and write to the
> file, but it refuses to show up in the directory listing. After I
> unmount the JFFS2 partition and remount it the file isn't there at
> all.

This is now fixed, isn't it? Is the 2.2 port now working completely?

--
dwmw2

      parent reply	other threads:[~2002-09-11 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 15:13 Problems unlinking files Chris AtLee
2002-06-19 23:33 ` David Woodhouse
2002-07-02 16:37   ` Chris AtLee
2002-09-11 13:42 ` 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=27421.1031751741@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=catlee@canada.com \
    --cc=linux-mtd@lists.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