From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs2 per directory quota
Date: Sun, 26 Jun 2011 13:46:28 +0200 [thread overview]
Message-ID: <201106261346.31869.dexen.devries@gmail.com> (raw)
In-Reply-To: <4E070070.1060502-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
Hi Niccolò,
On Sunday 26 June 2011 11:48:32 you wrote:
> I read nilfs2 does support per directory quota, but I didn't find how to
> achieve it: the few peoples who need directory quota do use xfs.
casually looking through NILFS2 sources, I don't see quota support, but I may
be wrong there. Why isn't XFS a viable option for you, if I may?
> Can you please give me some more info? Is nilfs2 still too much immature
> for a production environment?
I'm using it under light-to medium load for a few months now, both on desktops
and test server. In v2.6.39 it seems rock solid -- but that's just hear-say
evidence.
On caveat applies: under certain workload, current implementation suffer from
high file fragmentation. That workload for me is Bitcoin, which modifies a lot
of data in Berkley DB with pagesize 4kB. Also, BDB in Bitcoin issues fsync()
or similar after every disk write, which creates lots of checkpoints, eating
up diskspace with metadata.
But that's an extreme case; for general use NILFS2 is a-OK.
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 11:46 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 [this message]
[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
[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=201106261346.31869.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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).