All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 on 16TB goes read-only after "btrfs: block rsv returned -28"
Date: Wed, 05 Jun 2013 22:12:31 +0100	[thread overview]
Message-ID: <koo9jq$na8$1@ger.gmane.org> (raw)
In-Reply-To: <20130605162443.GE18160@twin.jikos.cz>

On 05/06/13 17:24, David Sterba wrote:
> On Wed, Jun 05, 2013 at 04:43:29PM +0100, Hugo Mills wrote:
>>    OK, so you've got plenty of space to allocate. There were some
>> issues in this area (block reserves and ENOSPC, and I think
>> specifically addressing the issue of ENOSPC when there's space
>> available to allocate) that were fixed between 3.8 and 3.9 (and
>> probably some between 3.9 and 3.10-rc as well), so upgrading your
>> kernel _may_ help here.
> 
> This is supposed to be fixed by
> https://patchwork-mail2.kernel.org/patch/2558911/
> 
> that went ti 3.10-rc with some followup patches, so it might not be
> enough as a standalone fix.
> 
> Unless you really need 'inode_cache', remove it from the mount options.

Thanks for that. Remounting without the inode_cache option looks to be
allowing rsync to continue. (No sync loop needed.)


For a 16TB raid1 on kernel 3.8.13, any good mount options to try?

For that size of storage and with many hard links, is there any
advantage formatting with leaf/node size greater than the default 4kBytes?


Thanks,
Martin


  reply	other threads:[~2013-06-05 21:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 14:57 btrfs raid1 on 16TB goes read-only after "btrfs: block rsv returned -28" Martin
2013-06-05 15:05 ` Hugo Mills
2013-06-05 15:28   ` Martin
2013-06-05 15:43     ` Hugo Mills
2013-06-05 15:59       ` Martin
2013-06-05 16:04         ` Hugo Mills
2013-06-05 16:24       ` David Sterba
2013-06-05 21:12         ` Martin [this message]
2013-06-07 23:14           ` Martin

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='koo9jq$na8$1@ger.gmane.org' \
    --to=m_btrfs@ml1.co.uk \
    --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 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.