Mailinglist Archive: opensuse-factory (554 mails)
| < Previous | Next > |
[opensuse-factory] SSD erased after fstrim
- From: Frank Kunz <mailinglists@xxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Jan 2016 20:47:00 +0100
- Message-id: <568D6F34.2040403@kunz-im-inter.net>
Hi,
I have some strange behavior while testing Tumbleweeed over the last two
weeks. I have seen it with different versions, also with the latest
20160105 a few minutes ago.
When doing a 'fstrim -v /' and then reboot I get a 'Non-System disc or
disk error,...' after that. It looks that the trim command trims a bit
more as it should do. I tested that on two different computers with
different SSDs. Both show the same fault. I had openSUSE 13.2 installed
before I switched to Tumbleweed and there was no problems with fstrim.
My disc configuration has no separate home partition, so all is btrfs.
My home directory is a btrfs subvolume with snapper timeline snapshots
enabled. Don't know if that is related to this issue.
Any ideas?
Br,
Frank
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
I have some strange behavior while testing Tumbleweeed over the last two
weeks. I have seen it with different versions, also with the latest
20160105 a few minutes ago.
When doing a 'fstrim -v /' and then reboot I get a 'Non-System disc or
disk error,...' after that. It looks that the trim command trims a bit
more as it should do. I tested that on two different computers with
different SSDs. Both show the same fault. I had openSUSE 13.2 installed
before I switched to Tumbleweed and there was no problems with fstrim.
My disc configuration has no separate home partition, so all is btrfs.
My home directory is a btrfs subvolume with snapper timeline snapshots
enabled. Don't know if that is related to this issue.
Any ideas?
Br,
Frank
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |