[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070719082516W.fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 19 Jul 2007 08:25:16 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: nix.or.die@...glemail.com
Cc: fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org,
jens.axboe@...cle.com, torvalds@...ux-foundation.org,
linux-scsi@...r.kernel.org
Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
From: Gabriel C <nix.or.die@...glemail.com>
Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
Date: Tue, 17 Jul 2007 03:40:58 +0200
> FUJITA Tomonori wrote:
> > From: Gabriel C <nix.or.die@...glemail.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.
I've not tested this yet (need to find sata drives in my workplace),
but James Bottomley told me that both works for him with bsg enabled.
It might worth trying the latest git tree.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists