All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: block rsv returned -28
Date: Sat, 25 Feb 2012 04:31:58 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.02.25.04.31.57@cox.net> (raw)
In-Reply-To: 4F4846E1.50307@polymtl.ca

Christian Robert posted on Fri, 24 Feb 2012 21:26:41 -0500 as excerpted:

> [ 1326.479217] hdparm: sending ioctl 330 to a partition!
> [ 1326.479219] hdparm: sending ioctl 330 to a partition!
> [ 1327.639153] parted: sending ioctl 1261 to a partition!
> [ 1327.639157] parted: sending ioctl 1261 to a partition!

FWIW, these warnings are expected ATM and don't have anything to do with 
btrfs.

They relate to kernel changes that will eventually result in increased 
strictness and security (hdparm won't be able to send suspend commands to 
a single partition, for instance, when it'll obviously apply to the whole 
drive), but are for now simply warnings, when whole-device commands are 
sent to a single partition instead of the whole device, thus allowing 
time for the necessary changes in userspace apps to be made.

There was an article about it in the LWN weekly edition some weeks ago.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      parent reply	other threads:[~2012-02-25  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  2:26 btrfs: block rsv returned -28 Christian Robert
2012-02-25  2:37 ` cwillu
2012-02-25  2:47   ` Christian Robert
2012-02-25  4:55     ` Duncan
2012-02-25  4:31 ` Duncan [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=pan.2012.02.25.04.31.57@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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 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.