From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: 3.10: discard/trim support on md-raid1?
Date: Sat, 13 Jul 2013 06:34:19 -0400 [thread overview]
Message-ID: <001701ce7fb4$889bdd40$99d397c0$@lucidpixels.com> (raw)
Hello,
Running 3.10 and I see the following for an md-raid1 of two SSDs:
Checking /sys/block/md1/queue:
add_random: 0
discard_granularity: 512
discard_max_bytes: 2147450880
discard_zeroes_data: 0
hw_sector_size: 512
iostats: 0
logical_block_size: 512
max_hw_sectors_kb: 32767
max_integrity_segments: 0
max_sectors_kb: 512
max_segment_size: 65536
max_segments: 168
minimum_io_size: 512
nomerges: 0
nr_requests: 128
optimal_io_size: 0
physical_block_size: 512
read_ahead_kb: 8192
rotational: 1
rq_affinity: 0
scheduler: none
write_same_max_bytes: 0
What should be seen:
rotational: 0
And possibly:
discard_zeroes_data: 1
Can anyone confirm if there is a workaround to allow TRIM when using
md-raid1?
Some related discussion here:
http://us.generation-nt.com/answer/md-rotational-attribute-help-206571222.ht
ml
http://www.progtown.com/topic343938-ssd-strange-itself-conducts.html
Justin.
WARNING: multiple messages have this Message-ID (diff)
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-raid@vger.kernel.org>
Subject: 3.10: discard/trim support on md-raid1?
Date: Sat, 13 Jul 2013 06:34:19 -0400 [thread overview]
Message-ID: <001701ce7fb4$889bdd40$99d397c0$@lucidpixels.com> (raw)
Hello,
Running 3.10 and I see the following for an md-raid1 of two SSDs:
Checking /sys/block/md1/queue:
add_random: 0
discard_granularity: 512
discard_max_bytes: 2147450880
discard_zeroes_data: 0
hw_sector_size: 512
iostats: 0
logical_block_size: 512
max_hw_sectors_kb: 32767
max_integrity_segments: 0
max_sectors_kb: 512
max_segment_size: 65536
max_segments: 168
minimum_io_size: 512
nomerges: 0
nr_requests: 128
optimal_io_size: 0
physical_block_size: 512
read_ahead_kb: 8192
rotational: 1
rq_affinity: 0
scheduler: none
write_same_max_bytes: 0
What should be seen:
rotational: 0
And possibly:
discard_zeroes_data: 1
Can anyone confirm if there is a workaround to allow TRIM when using
md-raid1?
Some related discussion here:
http://us.generation-nt.com/answer/md-rotational-attribute-help-206571222.ht
ml
http://www.progtown.com/topic343938-ssd-strange-itself-conducts.html
Justin.
next reply other threads:[~2013-07-13 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 10:34 Justin Piszcz [this message]
2013-07-13 10:34 ` 3.10: discard/trim support on md-raid1? Justin Piszcz
2013-07-13 10:47 ` Brad Campbell
2013-07-16 7:15 ` NeilBrown
2013-07-16 7:15 ` NeilBrown
2013-07-16 8:09 ` Justin Piszcz
2013-07-16 8:22 ` David Lang
2013-07-16 20:44 ` CoolCold
2013-07-17 1:48 ` NeilBrown
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='001701ce7fb4$889bdd40$99d397c0$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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.