From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Niccolò Belli" <darkbasic-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
Subject: Re: nilfs2 per directory quota
Date: Sun, 26 Jun 2011 14:48:29 +0200 [thread overview]
Message-ID: <201106261448.30236.dexen.devries@gmail.com> (raw)
In-Reply-To: <4E071EF5.1070301-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
Hi again,
On Sunday 26 June 2011 13:58:45 you wrote:
> Il 26/06/2011 13:46, dexen deVries ha scritto:
> > casually looking through NILFS2 sources, I don't see quota support, but I
> > may be wrong there.
>
> I read about per directory quotas in slashdot:
> http://linux.slashdot.org/comments.pl?sid=1287319&cid=28536529
I'm affraid the meaning of the post is ``I wish NILFS provided those:'' (the
``but how about having some real features'' bit).
> > Why isn't XFS a viable option for you, if I may?
>
> XFS *is* a viable option, but it was a chance to test a new fs ;)
I've been using XFS for several years, also in configuration with external
journal for extra performance. NILFS2 comes close, if not beter, in
performance in some cases; mostly for writting new data. For example, recently
checked out all linux kernel sources on a 5.400 RPM laptopd hdd, and it was
pretty darn fast. On the other hand, simply traversing the filesystem when
metadata is not cached can be slow.
Current implementation of NILFS2 has certain on-disk inefficiences in regard
to metadata, for example it doesn't use extents. The folks at NTT are working
on improving stuff.
You may also want to check out
http://en.wikipedia.org/wiki/Fossil_(file_system)
http://en.wikipedia.org/wiki/Venti
which are available on any POSIX environment via
http://en.wikipedia.org/wiki/Plan_9_port
I don't think Fossil provides any quota support, but when coupled with Venti,
it pretty much removes the need for it :P
Regards,
--
dexen deVries
> (...) I never use more than 800Mb of RAM. I am running Linux,
> a browser and a terminal.
rjbond3rd in http://news.ycombinator.com/item?id=2692529
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-26 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 9:48 nilfs2 per directory quota Niccolò Belli
[not found] ` <4E070070.1060502-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
2011-06-26 11:46 ` dexen deVries
[not found] ` <201106261346.31869.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-26 11:58 ` Niccolò Belli
[not found] ` <4E071EF5.1070301-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
2011-06-26 12:48 ` dexen deVries [this message]
[not found] ` <201106261448.30236.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-26 13:01 ` Niccolò Belli
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=201106261448.30236.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=darkbasic-DEeHIYRtcplPMsqi6aon0Q@public.gmane.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;
as well as URLs for NNTP newsgroup(s).