Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

On Fri, Aug 12, 2016 at 1:37 PM, Chris Murphy wrote: > On Fri, Aug 12, 2016 at 1:00 PM, Ronan Arraes Jardim Chagas > wrote: > > d. Run journalctl -f from a 2nd computer. Hopefully it's obvious I mean run journalctl -f on the affected computer

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

On Fri, Aug 12, 2016 at 1:00 PM, Ronan Arraes Jardim Chagas wrote: > Em Sex, 2016-08-12 às 12:02 -0600, Chris Murphy escreveu: >> Tons of unallocated space. What kernel messages do you get for the >> enospc? It sounds like this will be one of the mystery -28 error file >>

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

Em Sex, 2016-08-12 às 12:02 -0600, Chris Murphy escreveu: > Tons of unallocated space. What kernel messages do you get for the > enospc? It sounds like this will be one of the mystery -28 error file > systems. So far as I recall the only work around is recreating the > file system. There are two

[no subject]

Dear Sir/Madam I have a business proposal for you that will be of mutual benefit to both of us. It’s about the death of my late client and some money he left behind before his death. I want you to stand as his next of kin since you bear the same surname with him, so that the bank can

Re: BTRFS constantly reports "No space left on device" even with a huge unallocated space

On Fri, Aug 12, 2016 at 11:36 AM, Ronan Arraes Jardim Chagas wrote: > Hi guys, > > I'm facing a daily problem with BTRFS. Almost everyday, I get the > message "No space left on device". Sometimes I can recover by balancing > the system but sometimes even balancing does not work

[no subject]

Dear Sir/Madam I have a business proposal for you that will be of mutual benefit to both of us. It’s about the death of my late client and some money he left behind before his death. I want you to stand as his next of kin since you bear the same surname with him, so that the bank can

BTRFS constantly reports "No space left on device" even with a huge unallocated space

Hi guys, I'm facing a daily problem with BTRFS. Almost everyday, I get the message "No space left on device". Sometimes I can recover by balancing the system but sometimes even balancing does not work due to the lack of space. In this case, only a hard reset works if I can't delete some files.

Re: checksum error in metadata node - best way to move root fs to new drive?

On Fri, Aug 12, 2016 at 6:04 AM, Austin S. Hemmelgarn wrote: > On 2016-08-11 16:23, Dave T wrote: >> 5. Would most of you guys use btrfs + dm-crypt on a production file >> server (with spinning disks in JBOD configuration -- i.e., no RAID). >> In this situation, the data is

Re: checksum error in metadata node - best way to move root fs to new drive?

On 10 August 2016 at 23:21, Chris Murphy wrote: > > I'm using LUKS, aes xts-plain64, on six devices. One is using mixed-bg > single device. One is dsingle mdup. And then 2x2 mraid1 draid1. I've > had zero problems. The two computers these run on do have aesni > support.

Re: btrfs quota issues

Thanks for your inputs. Another question I had was, is there any way to check what's the directory/file sizes prior to compression and how much copression btrfs did, etc? Basicaly some stats around compression and/or dedupe from btrfs. On Thu, Aug 11, 2016 at 12:13 PM, Duncan

Re: checksum error in metadata node - best way to move root fs to new drive?

Austin S. Hemmelgarn posted on Fri, 12 Aug 2016 08:04:42 -0400 as excerpted: > On a file server? No, I'd ensure proper physical security is > established and make sure it's properly secured against network based > attacks and then not worry about it. Unless you have things you want to > hide

Re: [PATCH v3 2/3] btrfs: relocation: Fix leaking qgroups numbers on data extents

On Tue, Aug 9, 2016 at 9:30 AM, Qu Wenruo wrote: > When balancing data extents, qgroup will leak all its numbers for > relocated data extents. > > The relocation is done in the following steps for data extents: > 1) Create data reloc tree and inode > 2) Copy all data

Re: checksum error in metadata node - best way to move root fs to new drive?

On 2016-08-11 16:23, Dave T wrote: What I have gathered so far is the following: 1. my RAM is not faulty and I feel comfortable ruling out a memory error as having anything to do with the reported problem. 2. my storage device does not seem to be faulty. I have not figured out how to do more

Re: checksum error in metadata node - best way to move root fs to new drive?

On Thu, Aug 11, 2016 at 04:23:45PM -0400, Dave T wrote: > 1. Can one discontinue using the compress mount option if it has been > used previously? The mount option applies only to newly written blocks, and even then only to files that don't say otherwise (via chattr +c or +C, btrfs property,

Re: Strange behavior after "rm -rf //"

On Fri, 12 Aug 2016, Russell Coker wrote: > There are a variety of ways of giving the same result that rm > doesn't reject. "/*" Wasn't caught last time I checked. See the above > URL if you want to test out various rm operations as root. ;) Oh, yes - "rm -r /*" would work, even with a current