| To: | Liu Bo <bo.li.liu@xxxxxxxxxx> |
|---|---|
| Subject: | Re: fallocate mode flag for "unshare blocks"? |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 31 Mar 2016 00:55:29 -0700 |
| Cc: | "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-btrfs <linux-btrfs@xxxxxxxxxxxxxxx>, linux-api@xxxxxxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160331003242.GA5813@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <20160302155007.GB7125@xxxxxxxxxxxxx> <20160330182755.GC2236@xxxxxxxxxxxxxxxx> <20160331003242.GA5813@xxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Wed, Mar 30, 2016 at 05:32:42PM -0700, Liu Bo wrote: > Well, btrfs fallocate doesn't allocate space if it's a shared one > because it thinks the space is already allocated. So a later overwrite > over this shared extent may hit enospc errors. And this makes it an incorrect implementation of posix_fallocate, which glibcs implements using fallocate if available. |
| Previous by Date: | Re: fallocate mode flag for "unshare blocks"?, Christoph Hellwig |
|---|---|
| Next by Date: | Re: fallocate mode flag for "unshare blocks"?, Christoph Hellwig |
| Previous by Thread: | Re: fallocate mode flag for "unshare blocks"?, Liu Bo |
| Next by Thread: | Re: fallocate mode flag for "unshare blocks"?, Andreas Dilger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |