From: otakujunction@gmail.com
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Help with space
Date: Thu, 27 Feb 2014 14:49:40 -0600 [thread overview]
Message-ID: <B2988EF9-46EB-4804-A024-EE3B3A9E8771@gmail.com> (raw)
In-Reply-To: <82E08C64-154E-460E-A052-E60BC00D662C@colorremedies.com>
Yes it's an ancient 32 bit machine. There must be a complex bug involved as the system, when originally mounted, claimed the correct free space and only as used over time did the discrepancy between used and free grow. I'm afraid I chose btrfs because it appeared capable of breaking the 16 tera limit on a 32 bit system. If this isn't the case then it's incredible that I've been using this file system for about a year without difficulty until now.
-Justin
Sent from my iPad
> On Feb 27, 2014, at 1:51 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
>
>> On Feb 27, 2014, at 12:27 PM, Chris Murphy <lists@colorremedies.com> wrote:
>> This is on i686?
>>
>> The kernel page cache is limited to 16TB on i686, so effectively your block device is limited to 16TB. While the file system successfully creates, I think it's a bug that the mount -t btrfs command is probably a btrfs bug.
>
> Yes Chris, circular logic day. It's probably a btrfs bug that the mount command succeeds.
>
> So let us know if this is i686 or x86_64, because if it's the former it's a bug that should get fixed.
>
>
> Chris Murphy
>
> --
> 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:[~2014-02-27 20:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:19 Help with space Justin Brown
2014-02-27 19:27 ` Chris Murphy
2014-02-27 19:51 ` Chris Murphy
2014-02-27 20:49 ` otakujunction [this message]
2014-02-27 21:11 ` Chris Murphy
2014-02-28 0:12 ` Dave Chinner
2014-02-28 0:27 ` Chris Murphy
2014-02-28 4:21 ` Dave Chinner
2014-02-28 5:49 ` Chris Murphy
2014-02-28 4:34 ` Roman Mamedov
2014-02-28 7:27 ` Duncan
2014-02-28 7:37 ` Roman Mamedov
2014-02-28 7:46 ` Justin Brown
2014-05-01 1:52 ` Russell Coker
2014-05-01 5:33 ` Duncan
2014-05-02 1:48 ` Russell Coker
2014-05-02 8:23 ` Duncan
2014-05-02 9:28 ` Brendan Hide
2014-05-02 19:21 ` Chris Murphy
2014-05-02 21:08 ` Hugo Mills
2014-05-02 22:33 ` Chris Murphy
2014-05-03 16:31 ` Austin S Hemmelgarn
2014-05-03 19:09 ` Chris Murphy
2014-05-03 20:52 ` Austin S Hemmelgarn
2014-05-03 23:16 ` Chris Murphy
2014-02-28 6:13 ` Chris Murphy
2014-02-28 6:26 ` Chris Murphy
2014-02-28 7:39 ` Justin Brown
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=B2988EF9-46EB-4804-A024-EE3B3A9E8771@gmail.com \
--to=otakujunction@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox