From: Chris Murphy <lists@colorremedies.com>
To: nexus@smoula.net
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: ENOSPC while creating snapshot
Date: Fri, 4 Mar 2016 15:37:40 -0700 [thread overview]
Message-ID: <CAJCQCtRP6yNOk-oDy9dOiuTL1e19SB9H9cjueEZVsCwJS4vC6w@mail.gmail.com> (raw)
In-Reply-To: <c2e396477401f3441bdc364456b399f4@smoula.net>
On Fri, Mar 4, 2016 at 2:10 PM, <nexus@smoula.net> wrote:
> Hello,
>
> I'm encountering weird enospc problem while writing to filesystem and
> creating snapshot at a same time:
>
> Steps to reproduce:
>
> start writing data to filesystem:
>
> # LC_ALL=C dd if=/dev/zero of=/foobar
> dd: writing to '/foobar': No space left on device
> 3003803+0 records in
> 3003802+0 records out
> 1537946624 bytes (1.5 GB, 1.4 GiB) copied, 10.8072 s, 142 MB/s
>
> in other terminal create read-only (or r/w - results are the same)
> # btrfs sub snap -r / /.snap1
> Create a readonly snapshot of '/' in '//.snap1'
>
> while creating this snapshot, ENOSPC is produced.
Known issue. There's a thread already about it somewhere around here
in the last 4-6 weeks.
(rw,noatime,nodatasum,nodatacow,ssd,discard,space_cache,enospc_debug,commit=900,subvolid=5,subvol=/)
Most likely unrelated but commit time of 15 minutes? Umm, OK why?
--
Chris Murphy
next prev parent reply other threads:[~2016-03-04 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 21:10 ENOSPC while creating snapshot nexus
2016-03-04 22:37 ` Chris Murphy [this message]
[not found] ` <CAJ88j0axsFA3HFc6Cr5o-dtYxLau_iDS2Mx2uVzKvF5HCe9F5Q@mail.gmail.com>
2016-03-05 2:46 ` Chris Murphy
2016-03-05 5:34 ` Duncan
2016-03-05 10:24 ` Martin Mlynář
2016-03-04 22:49 ` Roman Mamedov
2016-03-05 2:09 ` Duncan
2016-03-05 10:46 ` Filipe Manana
2016-03-05 12:29 ` Martin Mlynář
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=CAJCQCtRP6yNOk-oDy9dOiuTL1e19SB9H9cjueEZVsCwJS4vC6w@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nexus@smoula.net \
/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).