| 1 |
On Wed, 12 Oct 2011 00:28:03 +0200 |
| 2 |
"Stefan G. Weichinger" <lists@×××××.at> wrote: |
| 3 |
|
| 4 |
> Am 12.10.2011 00:05, schrieb Alan McKinnon: |
| 5 |
> |
| 6 |
> > Yes, you misunderstand how fstrim works. It's not up to you to say |
| 7 |
> > what it does exactly, it's up to the drive firmware and possibly |
| 8 |
> > the kernel. It's actually fully described in the man page right |
| 9 |
> > there in the part for option -v :-) |
| 10 |
> |
| 11 |
> So it only tells me "something"? |
| 12 |
|
| 13 |
No, it's giving you a fact (and slightly misrepresenting it in the |
| 14 |
output). |
| 15 |
|
| 16 |
You asked the drive firmware for a favour - to please check if anything |
| 17 |
can be discarded and if so to discard it. |
| 18 |
|
| 19 |
<cue Mafia voice a la GodFather> |
| 20 |
|
| 21 |
The firmware checked that it *could* discard X bytes and then figured |
| 22 |
well, maybe it will, maybe it won't, maybe it'll do it on it's own |
| 23 |
good time, but what the heck - tell the user anyway how many bytes X |
| 24 |
is. Maybe that'll make the user happy so he'll stfu and go away...... |
| 25 |
|
| 26 |
The command leads you to believe the discard was actually done, but |
| 27 |
that's not necessarily true :-) |
| 28 |
|
| 29 |
It's probably a case of the drive knows much better than you what it |
| 30 |
should do. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Alan McKinnnon |
| 35 |
alan.mckinnon@×××××.com |
Archives