From: Gabriel C <nix.or.die@googlemail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com,
torvalds@linux-foundation.org, linux-scsi@vger.kernel.org
Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
Date: Tue, 17 Jul 2007 03:40:58 +0200 [thread overview]
Message-ID: <469C1E2A.8010508@googlemail.com> (raw)
In-Reply-To: <20070717100921W.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> From: Gabriel C <nix.or.die@googlemail.com>
> Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
> Date: Tue, 17 Jul 2007 02:44:38 +0200
>
>
>> Gabriel C wrote:
>>
>>> Hello,
>>>
>>> sdparm and hdparm are broken for me on git (
>>> abce891a10559343d8ac9f79b46d78afdba63a40 )
>>>
>>>
>>> ~$ sudo hdparm /dev/sdc
>>>
>>> /dev/sdc:
>>> BLKROGET failed: Inappropriate ioctl for device
>>> BLKRAGET failed: Inappropriate ioctl for device
>>> BLKGETSIZE failed: Inappropriate ioctl for device
>>>
>>>
>>> ~$ sudo sdparm --all /dev/sdc
>>> unable to access /dev/sdc, ATA disk?
>>>
>>>
>>>
>> Well it is bsg , setting BLK_DEV_BSG=n fixed all this errors.
>>
>
> Can you check the major number of your /dev/sdc? I've seen that
> /dev/sd* is linked to bsg devices somehow.
>
>
>
All my disks are doing this sdc was meant as example.
...
$ ls -la /dev/sd{a,b,c}
brw-r----- 1 root disk 8, 0 16. Jul 23:11 /dev/sda
brw-rw---- 1 root disk 8, 16 16. Jul 23:11 /dev/sdb
brw-r----- 1 root disk 8, 32 16. Jul 23:11 /dev/sdc
...
sd{a,b} are SCSI disks and sdc is an ATA disk.
You can get the used config from there :
http://194.231.229.228/2.6.22-gabce891a/config
Gabriel
next prev parent reply other threads:[~2007-07-17 1:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <469BD9C8.4000808@googlemail.com>
2007-07-17 0:44 ` Someone ( bsg merge ? ) broke {sd,hd}parm on current git Gabriel C
2007-07-17 1:09 ` FUJITA Tomonori
2007-07-17 1:40 ` Gabriel C [this message]
2007-07-18 23:25 ` FUJITA Tomonori
2007-07-19 0:48 ` Gabriel C
2007-07-19 14:02 ` James Bottomley
2007-07-19 14:31 ` Gabriel C
2007-07-19 15:19 ` James Bottomley
2007-07-19 15:48 ` Gabriel C
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=469C1E2A.8010508@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).