From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 106861] DPOFUA should not be related to WCE / Caching mode page
Date: Thu, 29 Oct 2015 08:15:26 +0000 [thread overview]
Message-ID: <bug-106861-11613-F8gSaqYTVA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106861-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106861
--- Comment #1 from Tom Yan <tom.ty89@gmail.com> ---
Example drive:
[tom@localhost ~]$ sudo sdparm --long /dev/sdc
/dev/sdc: WD My Passport 083A 1065
Direct access device specific parameters: WP=0 DPOFUA=1
Control [co] mode page:
SWP 0 [cha: n, def: 0, sav: 0] Software write protect
[tom@localhost ~]$ sudo sdparm -a --long /dev/sdc
/dev/sdc: WD My Passport 083A 1065
Direct access device specific parameters: WP=0 DPOFUA=1
Control [co] mode page:
TST 0 [cha: n, def: 0, sav: 0] Task set type
TMF_ONLY 0 [cha: n, def: 0, sav: 0] Task management functions only
DPICZ 0 [cha: n, def: 0, sav: 0] Disable protection information
check if protect field zero
D_SENSE 0 [cha: n, def: 0, sav: 0] Descriptor format sense data
GLTSD 0 [cha: n, def: 0, sav: 0] Global logging target save disable
RLEC 0 [cha: n, def: 0, sav: 0] Report log exception condition
QAM 1 [cha: n, def: 1, sav: 1] Queue algorithm modifier
NUAR 0 [cha: n, def: 0, sav: 0] No unit attention on release
QERR 0 [cha: n, def: 0, sav: 0] Queue error management
RAC 0 [cha: n, def: 0, sav: 0] Report a check
UA_INTLCK 0 [cha: n, def: 0, sav: 0] Unit attention interlocks control
SWP 0 [cha: n, def: 0, sav: 0] Software write protect
ATO 0 [cha: n, def: 0, sav: 0] Application tag owner
TAS 0 [cha: n, def: 0, sav: 0] Task aborted status
ATMPE 0 [cha: n, def: 0, sav: 0] Application tag mode page enabled
RWWP 0 [cha: n, def: 0, sav: 0] Reject write without protection
AUTOLOAD 0 [cha: n, def: 0, sav: 0] Autoload mode
BTP 0 [cha: n, def: 0, sav: 0] Busy timeout period (100us)
ESTCT 0 [cha: n, def: 0, sav: 0] Extended self test completion time
(sec)
Power condition [po] mode page:
PM_BG 0 [cha: n, def: 0, sav: 0] Power management, background
functions, precedence
STANDBY_Y 0 [cha: n, def: 0, sav: 0] Standby_y timer enable
IDLE_C 0 [cha: n, def: 0, sav: 0] Idle_c timer enable
IDLE_B 0 [cha: n, def: 0, sav: 0] Idle_b timer enable
IDLE 0 [cha: n, def: 0, sav: 0] Idle_a timer enable
STANDBY 1 [cha: y, def: 1, sav: 1] Standby_z timer enable
ICT 0 [cha: n, def: 0, sav: 0] Idle_a condition timer (100 ms)
SCT 18000 [cha: y, def:18000, sav:18000] Standby_z condition timer
(100 ms)
IBCT 0 [cha: n, def: 0, sav: 0] Idle_b condition timer (100 ms)
ICCT 0 [cha: n, def: 0, sav: 0] Idle_c condition timer (100 ms)
SYCT 0 [cha: n, def: 0, sav: 0] Standby_y condition timer (100 ms)
CCF_IDLE 0 [cha: n, def: 0, sav: 0] check condition on transition from
idle
CCF_STAND 0 [cha: n, def: 0, sav: 0] check condition on transition from
standby
CCF_STOPP 0 [cha: n, def: 0, sav: 0] check condition on transition from
stopped
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2015-10-29 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 8:14 [Bug 106861] New: DPOFUA should not be related to WCE / Caching mode page bugzilla-daemon
2015-10-29 8:15 ` bugzilla-daemon [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=bug-106861-11613-F8gSaqYTVA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 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).