Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Florian Gamböck" <ml@floga.de>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs changes (issues?) on OS upgrade
Date: Sat, 09 May 2015 10:43:53 +0200	[thread overview]
Message-ID: <554DC8C9.4020709@floga.de> (raw)
In-Reply-To: <1798034232.614027.1431151384353.JavaMail.apache@nm33.abv.bg>

Hi Milen,

Am 09.05.2015 um 08:03 schrieb Милен Христов:
> 2. After the upgrade I see the following entries in the kernel log(attached):
>
> [   78.717743]  sdb: unknown partition table
> [   78.735588]  sdc: unknown partition table
> [   78.736279]  sdd: unknown partition table
> [   78.781962]  sde: unknown partition table

I can't really tell you what is going on with the first problem, 
although I *guess* that it should be fine and is just the result of more 
accurate disk space calculations.

Regarding the second problem, I can confirm that I have the same 
messages in my log. It results from "formatting" the whole drive with 
BTRFS and not just a partition. So the drive has now no partition table 
which the kernel can identify. This does of course not change the fact 
that you can mount those drives without problems.

You didn't see those messages before, so my guess is, that between Ubu 
14.10 and 15.04 the kernel config was changed to make it more verbose. 
Do note, that those are not error or warning messages. The kernel is 
merely informing you about the fact, that it cannot identify the type of 
the partition table. Usually you can ignore those messages.

Regards
--Flo

  reply	other threads:[~2015-05-09  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09  6:03 Btrfs changes (issues?) on OS upgrade Милен Христов
2015-05-09  8:43 ` Florian Gamböck [this message]
2015-05-09  8:58 ` Tomasz Torcz
2015-05-11 16:32   ` David Sterba

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=554DC8C9.4020709@floga.de \
    --to=ml@floga.de \
    --cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox