On 06/19/2015 01:45 PM, Anton Aylward wrote:
On 06/19/2015 02:05 PM, Moby wrote:
Yes, the system is one big FS under / I realise that the designers envisioned something like this, but even with aggressive sub-volumes to handle partial backups, I think this stinks. it sets all my mental alarm bells running.
As you've seen, it anything goes wrong EVERYTHING goes wrong. There's a good reason we had partitioning!
I understand snapshotting can be carefully configured but the reality is that its obscure and awkward. The policy for something like zypper updates/patches and the ability to roll them back in the manner reminiscent of the mainframe era is distinct from the snapshotting for user space changes and possible accidental deletes. Snapshotting databases is, again, quite a different strategy.
I can see that a site that is, in effect, 'mainframe replacement' might warrant this and might warrant sending the admin off for relevant training and having a standby "scratch" system he could practice on (perhaps a virtual machine), but I think its overblown for a home user or just a workstation.
One headache, at least for me. is the journalctl business (I cannot just open up /var/log/messages). IIR there was a discussion of this earlier this year and some advice on how to run syslog to /var/log/messages in parallel. Hmm. I seem to be doing that :-) I must have paid attention at the time it was posted :-) Do check the archives ...
BTRFS package wise the system has: rpm -qa |grep btrf btrfsprogs-4.0-7.1.x86_64 libbtrfs0-4.0-7.1.x86_64 btrfsmaintenance-0.1-1.1.noarch I would strongly advise updating your kernel at the very least! There's the old adage about keeping patches up to date.
Try one of these. I prefer the first.
Kernel_Stable http://download.opensuse.org/repositories/Kernel:/stable/standard/ Kernel_standard
http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard/
I am fairly certain I can get balance to succeed after deleting "enough" stuff - key is what is "enough". I deleted yet another batch of data, and btrfs balance is now running, so far, with -dusage=100. Hmmm. This sounds rather like cutting off your arms and legs so as to reduce the amount of work the heart has to do pumping blood around the system.
I would really really really suggest installing a patched and up to date version of BtrFS - the kernel - as well as the utilities (see my earlier email for the repositories) rather than amputating your data.
Well, the machine is patched as per "standard" oss 132 repos (http://download.opensuse.org/repositories/openSUSE:/13.2:/Update/standard/). My prod systems all run syslog, this one machine I was trying to somewhat stay true to oss defaults (other than making the filesystem one big /). I have no problem adding the kernel and filesystem repos you mention (I have 3 other machines running tumbleweed with kernel from http://download.opensuse.org/repositories/Kernel:/stable/standard (those are at 4.0.5-4 as of this morning). This particular machine where btrfs balance is failing is still fully useable, just that balance keeps failing. My main reason for playing on this machine is really to see what type of setup to go with my prod servers when I upgrade those from 13.1 to 13.2 ... I normally stick with "stock" oss repos for prod systems (mainly just http://download.opensuse.org/repositories/openSUSE:/13.2:/Update/standard/ type stuff). I can easily rebuild the machine in question, the data is available elsewhere and is not in jeopardy). I have been deleting stuff and re-running balance, and I am at a point where it succeeds with -dusage=98 but fails with higher numbers. I am almost at the point to rule out using btrfs in my prod systems, rebuild this particular machine with ext4 on top of lvm on top of md, and then keep on going with my testing. One odd thing I noticed is that btrfs balance succeeds with -dusage=98, and fails with 99. However, if it I run it again with -dusage=98, it still "does stuff" and succeeds. Which makes me wonder if perhaps multiple passes are required with -dusage=98, at least until it stop reporting having done stuff. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org