From: Goffredo Baroncelli <kreijack@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Quota Clarification
Date: Mon, 1 Mar 2010 20:22:40 +0100 [thread overview]
Message-ID: <201003012022.41417.kreijack@libero.it> (raw)
In-Reply-To: <c5b98f841003010823k714af7bam94cabed9ed3c69cc@mail.gmail.com>
On Monday 01 March 2010, Robert LeBlanc wrote:
> On Fri, Feb 26, 2010 at 8:51 PM, Robert LeBlanc <robert@leblancnet.us>
wrote:
> > First off, thanks for the great work on btrfs. I've been trying to
> > follow the development for some time and now that Debian has
> > everything in Squeeze, I've been playing around with btrfs.
> >
> > I would like to implement btrfs on a large file server that we are
> > currently using ACLs, user and group quotas and LVM snapshots.
Pay attention that btrfs is under develop.
> > While
[...]
> > I went to look at the quotas and repquota said that the mount point
> > doesn't have quotas enabled. I then searched for documentation about
> > quotas and it was pretty sparse.
AFICT quota is not available in btrfs.
[...]
> I fail to see the benefit of having a btrfs root fs that is less than
> the disk or partition as the space can't be used for anything else. I
> hope I'm just doing something wrong here.
A possible application is shrinking a filesystem, in case of change of hard
disk.
>
> Thanks,
>
> Robert LeBlanc
> Life Sciences & Undergraduate Education Computer Support
> Brigham Young University
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
prev parent reply other threads:[~2010-03-01 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 3:51 Quota Clarification Robert LeBlanc
2010-03-01 16:23 ` Robert LeBlanc
2010-03-01 19:22 ` Goffredo Baroncelli [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=201003012022.41417.kreijack@libero.it \
--to=kreijack@gmail.com \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.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