All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: Marc MERLIN <marc@merlins.org>
Cc: 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:24:56 +0100	[thread overview]
Message-ID: <55DC88C8.9000203@friendlyvirus.org> (raw)
In-Reply-To: <20150825145922.GE20179@merlins.org>

Hi Marc,

On 25-08-2015 15:59, Marc MERLIN wrote:
>> 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
> 
> You're doing it wrong :)
> Upgrade/compile your own kernel without upgrading the OS.
>

I did try that once but didn't manage to do it, the kernel upgrade broke
other stuff. I'm a bit more experienced then complete newbie (hence
using btrfs), but still very far from knowledable user, so I don't doubt
it can be done. Indeed, using btrfs might be seen as a wrong move in my
case, which I understand, although on the other hand btrfs saved me many
times from other begginer mistakes by allowing a simple restore by just
renaming snapshots.

>> block group 32...... flags 36'). This is a OCZ vertex 3, a quite fast SSD.
> 
> I've had 5 (yes 5, I replaced my drive 4 times) OCZ Vertex 4 drives, and
> they all gave me corruption with btrfs on unclean power down. The last
> one didn't work any better, I just gave up and went to Samsung EVO 840
> and those have been fine.

Ok, I've been warned then. I'm glad to know about the samsung EVO
though, I've been eyeing buying two of those for a raid1 system. Then I
would solve two issues in one go !

Best,
Miguel Negrão


  reply	other threads:[~2015-08-25 15:31 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 [this message]
2015-08-25 15:43   ` Austin S Hemmelgarn
2015-08-25 15:17 ` Matt Ruffalo
2015-08-25 15:53   ` Miguel Negrão

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=55DC88C8.9000203@friendlyvirus.org \
    --to=miguel.negrao-lists@friendlyvirus.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.