From: "Vincent Olivier" <vincent@up4.com>
To: "Duncan" <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: errors while "btrfs receive"
Date: Tue, 1 Sep 2015 13:31:46 -0400 (EDT) [thread overview]
Message-ID: <1441128706.141824093@apps.rackspace.com> (raw)
In-Reply-To: <pan$e8554$6dbe382c$ff1dc29$3d51b79e@cox.net>
It's ~900GiB. Sorry.
I'm on 4.1.6 Arch Linux.
-----Original Message-----
From: "Duncan" <1i5t5.duncan@cox.net>
Sent: Tuesday, September 1, 2015 03:30
To: linux-btrfs@vger.kernel.org
Subject: Re: errors while "btrfs receive"
Vincent Olivier posted on Mon, 31 Aug 2015 14:34:02 -0400 as excerpted:
> i'm doing a ~900TiB receive on a 6x4TB RAID0
>
> "fi show", "device scan" all fail and report "unable to connect to
> /dev/sdX"
>
> is it normal ?
Can't answer your direct question as my use-case doesn't include send/
receive, but...
~900TiB receive on a 24TB (6x4TB) raid0?
Did you mean ~900GiB, or did you miss the decimal point, or ???? I mean,
yeah, btrfs does have the compress= option, but I don't think it's going
to compress 900 TiB to fit in under 24! That's likely to be some
seriously lossy compression!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
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
prev parent reply other threads:[~2015-09-01 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 18:34 errors while "btrfs receive" Vincent Olivier
2015-09-01 7:30 ` Duncan
2015-09-01 17:31 ` Vincent Olivier [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=1441128706.141824093@apps.rackspace.com \
--to=vincent@up4.com \
--cc=1i5t5.duncan@cox.net \
--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.