From: ST <smntov@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: quotas: failure on removing a file via SFTP/SSH
Date: Tue, 21 Nov 2017 15:18:12 +0200 [thread overview]
Message-ID: <1511270292.1680.35.camel@gmail.com> (raw)
In-Reply-To: <093ee7e4-91f1-7d23-1ef1-81230d07b405@gmx.com>
On Tue, 2017-11-21 at 20:28 +0800, Qu Wenruo wrote:
>
> On 2017年11月21日 20:08, ST wrote:
> > Hello,
> >
> > I'm trying to use quotas for a simple chrooted sftp setup, limiting
> > space for each user's subvolume (now for testing to 1M).
> >
> > I tried to hit the limit by uploading files and once it comes to the
> > limit I face following problem: if I try to free space by removing a
> > file via Linux sftp client (or Filezilla) - I get error:
> > "Couldn't delete file: Failure"
> >
> > Sometimes, but not always, if I repeat it for 3-5 times it does removes
> > the file at the end.
> > If I login as root and try to remove the file via SSH I get the error:
> > "rm: cannot remove 'example.txt': Disk quota exceeded"
> >
> > What is the problem? And how can I solve it?
>
> Kernel version first.
>
> If it's possible, please use latest kernel, at least newer than v4.10,
> since we have a lot of qgroup reservation related fixes in newer kernel.
>
> Then, for small quota, due to the nature of btrfs metadata CoW and
> relative large default node size (16K), it's quite easy to hit disk
> quota for metadata.
Yes, but why I get the error specifically on REMOVING a file? Even if I
hit disk quota - if I free up space - it should be possible, isn't it?
> >
> >
> > --
> > 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
> >
>
next prev parent reply other threads:[~2017-11-21 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 12:08 quotas: failure on removing a file via SFTP/SSH ST
2017-11-21 12:25 ` Lakshmipathi.G
2017-11-21 13:16 ` ST
2017-11-21 12:28 ` Qu Wenruo
2017-11-21 13:18 ` ST [this message]
2017-11-21 14:34 ` Qu Wenruo
2017-11-21 15:29 ` ST
2017-11-21 18:33 ` Chris Murphy
2017-11-21 21:00 ` ST
2017-11-22 0:39 ` Qu Wenruo
2017-11-22 8:32 ` ST
2017-11-22 9:01 ` Qu Wenruo
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=1511270292.1680.35.camel@gmail.com \
--to=smntov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.