On 2014-12-04 09:25, Shriramana Sharma wrote:
Shouldn't be a problem, but unless they have changed the behavior recently specifying a filter for metadata also runs with that filter for system chunks unless you explicitly specify a different filter set for those. The reason for the warning regarding system chunks is that if they get messed up, you pretty much lose everything on the disk.On Thu, Dec 4, 2014 at 7:43 PM, Austin S Hemmelgarn <ahferro...@gmail.com> wrote:SuSE may have an old version of btrfs-progs then (which wouldn't surprise me, it is an 'enterprise' distribution after all), because I haven't seen this on anything since 3.16.Well OK I kinda like the "old" name SuSE since that was the name I was using back when I was on 9.3, but actually I'm running openSUSE Tumbleweed. See: $ btrfs --version Btrfs v3.17+20141103 I suppose Tumbleweed should be short and clear enough for my future usage.Also, for future reference, you can use the switch -mprofiles=single to just balance out those chunks.Wow, thanks, that returned quickly. (Thankfully I did btrfs bal from a separate terminal can rather than ^C.) BTW I thought you had unintentionally (for brevity) omitted the -sprofiles=single and I gave it but it complained saying: Refusing to explicitly operate on system chunks. Pass --force if you really want to do that. So I did give --force. (Is it the same as -f?) I hope that was OK?
smime.p7s
Description: S/MIME Cryptographic Signature
