From: Michael Clark <michael@metaparadigm.com>
To: Steve French <smfrench@austin.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: automated filesystem testing for multiple Linux fs
Date: Fri, 17 Dec 2004 10:23:58 +0800 [thread overview]
Message-ID: <41C2433E.4040402@metaparadigm.com> (raw)
In-Reply-To: <41C22D93.3030101@austin.rr.com>
Steve French wrote:
> Michael Clark wrote:
>
>> Steve French wrote:
>>
>>> ... Since
>>> at present only XFS and JFS have the full combination of server
>>> features: better quotas, DMAPI, xattr support, ACL support and
>>> nanosecond file timestamps on disk
>>>
>>
>> Does JFS have quota support now?
>>
>> Last I looked it was still on the To Do list.
>>
>> ~mc
>>
> I remember them adding it four months ago or so. Looking at
> http://linux.bkbits.net/linux-2.5
> it seems to be mostly in changeset 1.1803.133.1
Oh, that's good news. This was one reason you couldn't really consider
using JFS on a /home fileserver (which sort of implies quotas). It
perhaps it needs a lot of testing as it's quite new. Any experiences?
(ie. survives a highly parallel load from a lot of threads with
different uids).
~mc
next prev parent reply other threads:[~2004-12-17 2:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 16:56 cifs large write performance improvements to Samba Steve French
2004-12-13 17:20 ` cliff white
2004-12-13 18:34 ` Steve French
2004-12-13 18:43 ` Steve French
2004-12-16 12:11 ` Marcelo Tosatti
2004-12-16 16:39 ` automated filesystem testing for multiple Linux fs Steve French
2004-12-17 0:27 ` Michael Clark
2004-12-17 0:51 ` Steve French
2004-12-17 2:23 ` Michael Clark [this message]
2004-12-16 18:58 ` cifs large write performance improvements to Samba Hans Reiser
2004-12-16 16:30 ` Marcelo Tosatti
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=41C2433E.4040402@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@austin.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox