Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-25 Thread Lutz Vieweg
On 08/05/2016 10:03 PM, Gabriel C wrote: On 04.08.2016 18:53, Lutz Vieweg wrote: I was today hit by what I think is probably the same bug: A btrfs on a close-to-4TB sized block device, only half filled to almost exactly 2 TB, suddenly says "no space left on device" upon any attempt to write to

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-05 Thread Gabriel C
On 04.08.2016 18:53, Lutz Vieweg wrote: > > I was today hit by what I think is probably the same bug: > A btrfs on a close-to-4TB sized block device, only half filled > to almost exactly 2 TB, suddenly says "no space left on device" > upon any attempt to write to it. The filesystem was NOT

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-05 Thread Lutz Vieweg
On 08/05/2016 02:12 PM, Austin S. Hemmelgarn wrote: > If you stick to single disk We do, all our btrfs filesystems reside on one single block device, redundancy is provided by a DRBD layer below. > don't use quota groups We don't use any quotas. > stick to reasonably sized filesystems (not

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-05 Thread Austin S. Hemmelgarn
On 2016-08-05 06:56, Lutz Vieweg wrote: On 08/04/2016 10:30 PM, Chris Murphy wrote: Keep in mind the list is rather self-selecting for problems. People who aren't having problems are unlikely to post their non-problems to the list. True, but the number of people inclined to post a bug report

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-05 Thread Lutz Vieweg
On 08/04/2016 10:30 PM, Chris Murphy wrote: Keep in mind the list is rather self-selecting for problems. People who aren't having problems are unlikely to post their non-problems to the list. True, but the number of people inclined to post a bug report to the list is also a lot smaller than

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-04 Thread Chris Murphy
On Thu, Aug 4, 2016 at 10:53 AM, Lutz Vieweg wrote: > The amount of threads on "lost or unused free space" without resolutions > in the btrfs mailing list archive is really frightening. If these > symptoms commonly re-appear with no fix in sight, I'm afraid I'll have > to either

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-08-04 Thread Lutz Vieweg
Hi, I was today hit by what I think is probably the same bug: A btrfs on a close-to-4TB sized block device, only half filled to almost exactly 2 TB, suddenly says "no space left on device" upon any attempt to write to it. The filesystem was NOT automatically switched to read-only by the kernel,

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-01-01 Thread cheater00 .
here is the info requested, if that helps anyone. # uname -a Linux SX20S 4.3.0-040300rc7-generic #201510260712 SMP Mon Oct 26 11:27:59 UTC 2015 i686 i686 i686 GNU/Linux # aptitude show btrfs-tools Package: btrfs-tools State: installed Automatically installed: no Version:

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2016-01-01 Thread cheater00 .
I have been unable to reproduce so far. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2015-12-30 Thread cheater00 .
Hi, I have a 6TB partition here, it filled up while still just under 2TB were on it. btrfs fi df showed that Data is 1.92TB: Data, single: total=1.92TiB, used=1.92TiB System, DUP: total=8.00MiB, used=224.00KiB System, single: total=4.00MiB, used=0.00B Metadata, DUP: total=5.00GiB, used=3.32GiB

Re: 6TB partition, Data only 2TB - aka When you haven't hit the "usual" problem

2015-12-30 Thread Chris Murphy
kernel and btrfs-progs versions and output from: 'btrfs fi show ' 'btrfs fi usage ' 'btrfs-show-super ' 'df -h' Then umount the volume, and mount with option enospc_debug, and try to reproduce the problem, then include everything from dmesg from the time the volume was mounted. -- Chris Murphy