From: Dave Jones <davej@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
rdunlap@xenotime.net
Subject: Re: RFC: Schedule EFS for removal.
Date: Mon, 21 May 2007 11:09:37 -0400 [thread overview]
Message-ID: <20070521150937.GB6957@redhat.com> (raw)
In-Reply-To: <20070521150242.GA25146@infradead.org>
On Mon, May 21, 2007 at 04:02:42PM +0100, Christoph Hellwig wrote:
> On Mon, May 21, 2007 at 10:46:18AM -0400, Dave Jones wrote:
> > EFS aparently is broken (See http://bugzilla.kernel.org/show_bug.cgi?id=1020)
> > has been so for some time, and attempts to fix it have been rejected.
> > Given there's a userspace app to access these volumes, how
> > about scheduling it for removal ?
>
> It works perfectly fine, just not with the odd blocksizes on cdroms.
> SGI Australia folks are using it for exporting their irix cdrom images
> to various nfs systems for example, and I added that support long after
> the bug was opened.
>
> So clear NACK for this.
Ah, that woke people up :-)
Ok, patch rescinded. Any opinion on what to do about that bug?
"use loopback" would be one option I guess.
Given its been an open bug for four years, there's obviously
not that much interest in fixing the filesystem.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-05-21 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 14:46 RFC: Schedule EFS for removal Dave Jones
2007-05-21 15:02 ` Christoph Hellwig
2007-05-21 15:09 ` Dave Jones [this message]
2007-05-21 15:12 ` Christoph Hellwig
2007-05-21 15:20 ` Dave Jones
2007-05-21 15:46 ` Christoph Hellwig
2007-05-21 17:11 ` Dave Jones
2007-05-21 17:12 ` Christoph Hellwig
2007-05-21 17:25 ` Randy Dunlap
2007-05-22 21:01 ` Willy Tarreau
2007-05-22 22:49 ` Dave Jones
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=20070521150937.GB6957@redhat.com \
--to=davej@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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