From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: Matt Ruffalo <matt.ruffalo@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs tragedy: lack of space for metadata leads to loss of fs.
Date: Tue, 25 Aug 2015 16:53:56 +0100 [thread overview]
Message-ID: <55DC8F94.1020200@friendlyvirus.org> (raw)
In-Reply-To: <55DC8718.8060209@gmail.com>
On 25-08-2015 16:17, Matt Ruffalo wrote:
> 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.
Oh, that's very good advice. Running 3.19 now, great thanks ! When 4.1
comes out will update.
Thanks !
Miguel
prev parent reply other threads:[~2015-08-25 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 13:44 Btrfs tragedy: lack of space for metadata leads to loss of fs Miguel Negrão
2015-08-25 14:00 ` Austin S Hemmelgarn
2015-08-25 14:26 ` Miguel Negrão
2015-08-25 14:53 ` Austin S Hemmelgarn
2015-08-25 14:59 ` Marc MERLIN
2015-08-25 15:24 ` Miguel Negrão
2015-08-25 15:43 ` Austin S Hemmelgarn
2015-08-25 15:17 ` Matt Ruffalo
2015-08-25 15:53 ` Miguel Negrão [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55DC8F94.1020200@friendlyvirus.org \
--to=miguel.negrao-lists@friendlyvirus.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=matt.ruffalo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).