All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Mismatch between hdaprm and sdparm output
Date: Mon, 07 Aug 2006 10:32:26 +1000	[thread overview]
Message-ID: <23691.1154910746@ocs3.ocs.com.au> (raw)

NEC Versa S5200 laptop with FUJITSU MHV2080B SATA disk.  Kernel
2.6.16.21-0.13-smp (suselinux 10.1) using ata_piix.  hdparm and sdparm
give inconsistent results, which one should I believe?  My main concern
is write caching (XFS filesystem).

hdparm -I

/dev/sda:

ATA device, with non-removable media
	Model Number:       FUJITSU MHV2080BH
	Serial Number:      NW28T62255WF
	Firmware Revision:  00000028
Standards:
	Supported: 7 6 5 4
	Likely used: 7
Configuration:
	Logical		max	current
	cylinders	16383	16383
	heads		16	16
	sectors/track	63	63
	--
	CHS current addressable sectors:   16514064
	LBA    user addressable sectors:  156301488
	LBA48  user addressable sectors:  156301488
	device size with M = 1024*1024:       76319 MBytes
	device size with M = 1000*1000:       80026 MBytes (80 GB)
Capabilities:
	LBA, IORDY(can be disabled)
	Queue depth: 32
	Standby timer values: spec'd by Standard, no device specific minimum
	R/W multiple sector transfer: Max = 16	Current = 16
	Advanced power management level: 128 (0x80)
	Recommended acoustic management value: 254, current value: 254
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4
	     Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	READ BUFFER cmd
	   *	WRITE BUFFER cmd
	   *	Host Protected Area feature set
	   *	Look-ahead
		Write cache
	   *	Power Management feature set
		Security Mode feature set
	   *	SMART feature set
	   *	FLUSH CACHE EXT command
	   *	Mandatory FLUSH CACHE command
	   *	Device Configuration Overlay feature set
	   *	48-bit Address feature set
	   *	Automatic Acoustic Management feature set
	   *	SET MAX security extension
	   *	Advanced Power Management feature set
	   *	DOWNLOAD MICROCODE cmd
	   *	General Purpose Logging feature set
	   *	SMART self-test
	   *	SMART error logging
Security:
	Master password revision code = 65534
		supported
	not	enabled
	not	locked
		frozen
	not	expired: security count
	not	supported: enhanced erase
	80min for SECURITY ERASE UNIT.
Checksum: correct


sdparm --get=WCE

    /dev/sda: ATA       FUJITSU MHV2080B  0000
WCE         1

hdparm -A 1/0 can set/clear write cache, sdparm --set=WCE=0/1 always
gets an error:

sdparm --set=WCE=0 /dev/sda
    /dev/sda: ATA       FUJITSU MHV2080B  0000
    change_mode_page: failed setting page: Caching (SBC)


             reply	other threads:[~2006-08-07  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  0:32 Keith Owens [this message]
2006-08-07  0:42 ` Mismatch between hdaprm and sdparm output Arjan van de Ven

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=23691.1154910746@ocs3.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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.