Re: Btrfs tragedy: lack of space for metadata leads to loss of fs.

[Matt Ruffalo <matt.ruffalo@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

On 2015-08-25 09:44, Miguel Negrão wrote:
> Hi list,
>
> This weekend had my first btrfs horror story. 
>
> system: 3.13.0-49-lowlatency, btrfs-progs v4.1.2
>
> A disclaimer: I know 3.13 is very out of date, but I the requirement of
> keeping kernel up to date clashes with my requirement of keeping a stable
> system. At the moment I can't disturb my system as I'm doing important work,
> upgrading kernel requires upgrading ubuntu, which will upgrade a lot of
> packages and might lead to problems which I don't have time to fix. One
> might argue that in the end I lost time anyway dealing with these btrfs
> issues. When I'm done with this current work I will update the whole system
> which will update the kernel in the process.

Hi-

I have no useful advice about filesystem recovery, but would like to
point out that newer kernels are backported to Ubuntu LTS versions and
can be installed without any significant disruption of the system.

The normal kernel backports are named 'linux-generic-lts-<version
codename>', and the low latency versions are
'linux-lowlatency-lts-<version codename>', so you could install kernel
3.16 (from 14.10 "utopic") by installing linux-lowlatency-lts-utopic,
and kernel 3.19 (from 15.04 "vivid") by installing
linux-lowlatency-lts-vivid. Kernel 4.1 will be available as
linux-{generic,lowlatency}-lts-wily a bit after 15.10 is released.

MMR...


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]