Mailinglist Archive: opensuse-project (479 mails)

< Previous Next >
[opensuse-project] openSUSE 11.3, disk expert needed (SSD + hdparm/wiper.sh error: /usr/sbin/rdev needed but not found)
  • From: Johannes Nohl <johannes.nohl@xxxxxxxxx>
  • Date: Wed, 12 Jan 2011 17:29:58 +0100
  • Message-id: <AANLkTi=C9iypYysvOqCuGTgK68sP6Trty0qaQ5t7CT3D@mail.gmail.com>
I'd like to ask for feedback. How do you treat your SSD running
openSUSE 11.3? By now it is recommended
(http://en.opensuse.org/SDB:SSD_discard_%28trim%29_support) to run
wiper.sh for discarding free space weekly. This is at least true as
long there's no native TRIM-support which is compatible to modern
SSDs.

openSUSE 11.3 is shipping with hdparm updated to version 9.36. The
script /sbin/wiper.sh is included there. Am I the only one
experiencing this error:

wiper.sh: Linux SATA SSD TRIM utility, version 3.1, by Mark Lord.
wiper.sh: This tool is DANGEROUS! Please read and understand
wiper.sh: /usr/share/doc/packages/hdparm/README.wiper
wiper.sh: before going any further.
/usr/sbin/rdev: needed but not found, aborting.

How do you deal with it? rdev (as far as I understand) doesn't come
with openSUSE anymore. Additionally it does only return the name of
the root device "/dev/sdXX".

Possible solution: Add the following two lines at line 260 of
/sbin/wiper.sh (in diff):

261,262d260
< elif [ "$RDEV" == "" -a `$GAWK '{if ($2 ~ /^\/$/) print $1}'
/etc/mtab` != "" ]; then
< rootdev=`$GAWK '{if ($2 ~ /^\/$/) print $1}' /etc/mtab` ## openSUSE

This will make the script reading root device from /etc/mtab.

I only tried to run the script in dry mode. Is there any harm with
that solution? Should I go real with it? I guess it's only a minor
issue. Btw if it's of any interested: I own a OCZ Vertex 2 Extended.


I tried to bring this upstream. But the bug tracker on
hdparm.sourceforge.net doesn't look like very much populated...

Greetings
Johannes
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups