linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <boaz@plexistor.com>
To: Jens Axboe <axboe@fb.com>, Tony Luck <tony.luck@gmail.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
	Dmitry Monakhov <dmonakhov@openvz.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 3/4 v4] brd: Fix all partitions BUGs
Date: Sun, 18 Jan 2015 15:08:24 +0200	[thread overview]
Message-ID: <54BBB048.7010207@plexistor.com> (raw)
In-Reply-To: <54B99591.7080007@fb.com>

On 01/17/2015 12:49 AM, Jens Axboe wrote:
> On 01/16/2015 03:32 PM, Tony Luck wrote:
>> On Wed, Jan 7, 2015 at 8:07 AM, Boaz Harrosh <boaz@plexistor.com> wrote:
>>> From: Boaz Harrosh <boaz@plexistor.com>
>>>
>>> This patch fixes up brd's partitions scheme, now enjoying all worlds.
>>
>> linux-next-20150116 includes this as commit
>> 937af5ecd0591e84ee54180fa97dcbe9bbe5fed6
>>
>> On ia64 I'm seeing:
>> ram0: unknown partition table
>> ram1: unknown partition table
>> ...
>> ram15: unknown partition table
>>
>> At first I blamed c8fa31730fc7 "brd: Request from fdisk 4k alignment" because it
>> has all sorts of comments about PAGE_SIZE and 4k ... and my page size isn't
>> 4k.  But, reverting that one didn't help.
>>
>> reverting 937af5ecd0 does make the message go away.
> 
> Boaz, why wasn't GENHD_FL_SUPPRESS_PARTITION_INFO retained?
> 

OK. This message is completely harmless. My vm's 3 FSfull devices
print this message day in and day out. Its when you have an FS on
a partition-less device.

Dmitry had a module param "show_partition" which controls the addition
of this flag. The reason to remove it is because for some reason
with it, mount by UUID would not work, same reason lsblk would not see
the partition on this device even with -a.

For some reason GENHD_FL_SUPPRESS_PARTITION_INFO does not only shut up
that harmless message above, it interferes with any partition operations.
(As well as any udev operation on the device)

Do you want that I add back Dmitry's "show_partition" module param? Or should
I add a new flag that would behave exactly as a regular device but only
suppress the above harmless and annoying message like:
	GENHD_FL_PARTITION_LESS_OK (Or something like that)

Your call, Tell me which way you want to go. For me the message above is a
daily routine with many other devices not only brd. 
(I would even just remove the message above, what is it for at all? What error
condition does it uncover? So OK I have plugged a new device and it is
uninitialized yet, how the "unknown partition table" helps me in anyway?
I'm not complaining I would really like to understand.)

Thanks
Boaz


  reply	other threads:[~2015-01-18 13:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 16:02 [PATCHSET 0/4 v4] brd: partition fixes Boaz Harrosh
2015-01-07 16:04 ` [PATCH 1/4 v4] axonram: Fix bug in direct_access Boaz Harrosh
2015-01-07 16:05 ` [PATCH 2/4 v4] block: Change direct_access calling convention Boaz Harrosh
2015-01-07 16:07 ` [PATCH 3/4 v4] brd: Fix all partitions BUGs Boaz Harrosh
2015-01-16 22:32   ` Tony Luck
2015-01-16 22:49     ` Jens Axboe
2015-01-18 13:08       ` Boaz Harrosh [this message]
2015-01-18 15:10         ` Christoph Hellwig
2015-01-18 15:32           ` [RFC] block: Remove annoying "unknown partition table" message Boaz Harrosh
2015-01-18 15:48             ` Boaz Harrosh
2015-01-20 21:50               ` Jens Axboe
2015-01-22 12:39                 ` [PATCH] " Boaz Harrosh
2015-01-22 12:47                   ` Boaz Harrosh
2015-01-07 16:09 ` [PATCH 4/4 v4] brd: Request from fdisk 4k alignment Boaz Harrosh
2015-01-08 15:37   ` Martin K. Petersen
2015-01-08 20:56 ` [PATCHSET 0/4 v4] brd: partition fixes Jens Axboe
2015-01-11  9:30   ` Boaz Harrosh

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=54BBB048.7010207@plexistor.com \
    --to=boaz@plexistor.com \
    --cc=axboe@fb.com \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=tony.luck@gmail.com \
    --cc=willy@linux.intel.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).