Bug 575143 - WD20EARS hd reports wrong physical sector size, alignment and probably io_size values in /sys/block/sd?
Summary: WD20EARS hd reports wrong physical sector size, alignment and probably io_siz...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-19 15:29 UTC by Till Maas
Modified: 2011-06-27 15:20 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:13:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
script to gather device info, use "sdb" as parameter (497 bytes, text/plain)
2010-03-19 15:32 UTC, Till Maas
no flags Details
results from the script with the jumper set, i.e. the sectors are shifted (4.70 KB, text/plain)
2010-03-19 15:33 UTC, Till Maas
no flags Details
results from the script without the jumper set (4.82 KB, text/plain)
2010-03-19 15:34 UTC, Till Maas
no flags Details

Description Till Maas 2010-03-19 15:29:00 UTC
Description of problem:
The WD20EARS uses 4096 byte sectors internally, but reports to have 512 byte sectors. It also support enabling an 512 byte offset using a jumper.

Version-Release number of selected component (if applicable):
2.6.33-0.52.rc8.git6.fc13.i686

Steps to Reproduce:
1. run the script I will attach once with and once without PINS 8 and 9 connected on the drive
  
Actual results:
- physical sector size is 512
- alignment is always 0
- io_size is 512

Expected results:
- physical sector size should be 4096
- alignment should be 512 (afaik) if the jumper is set.
- the io_size values should be probably 4096, too. But 65536 seems to be a good value, too. (Determined using dd with different block sizes for writing)

Additional info:
This is probably a hardware bug, but I was asked by Ric Wheeler to open a bug to track status.

Comment 1 Till Maas 2010-03-19 15:32:51 UTC
Created attachment 401268 [details]
script to gather device info, use "sdb"  as parameter

Comment 2 Till Maas 2010-03-19 15:33:34 UTC
Created attachment 401269 [details]
results from the script with the jumper set, i.e. the sectors are shifted

Comment 3 Till Maas 2010-03-19 15:34:01 UTC
Created attachment 401270 [details]
results from the script without the jumper set

Comment 5 Chuck Ebbert 2010-04-09 17:01:52 UTC
The patch in comment #4 went in 2.6.33-rc7, so that's not the fix.

Comment 6 Karel Zak 2010-04-26 07:39:02 UTC
It seems that some users have a better results with newer WD disks:
http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/3160

Comment 7 Eric Sandeen 2011-05-13 01:30:10 UTC
Hrm, I have a recent disk:

	Model Number:       WDC WD20EARS-00MVWB0                    
	Firmware Revision:  51.0AB51

and it's exactly the same.  512/512 and no indication of offset (or not).

I think we need a WD contact...

Comment 8 Bug Zapper 2011-06-02 16:04:14 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2011-06-27 15:13:23 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 10 Eric Sandeen 2011-06-27 15:20:19 UTC
WONTFIX is fine; this is likely a hardware/firmware issue in any case.


Note You need to log in before you can comment on or make changes to this bug.