I have a laptop with a 1TB SSD.
The smartd daemon logs an error each hour as follows:
-=-=-=->
Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Device info:
CT1000MX500SSD4, S/N:2027E2B39329, WWN:5-00a075-1e2b39329, FW:M3CR023,
1.00 TB
For details see host's SYSLOG.
-=-=-=->
May I suggest that Diego Iastrubni be removed from this mailing list
due to potential future disruption of public peace by asking for
removal of people, who have been framed by powerful business
competitors?
--- Omer Zak
On Tue, 2021-05-04 at 22:06 +0300, Shay Gover wrote:
> Please do not
Please do not assume that you can speak for the community based on an
article at Ynet.
There is no verdict in that case, not even a complaint (Checked on Nevo
now). Just a rumor and someone wealthy enough to post it on Ynet.
-- Forwarded message -
From: Ori Idan
Date: Tue, May
Sorry, I am not a convicted criminal.
If you believe what is written in Yediot, that is your problem.
--
Ori Idan CEO Helicon Books
http://www.heliconbooks.com
On Tue, May 4, 2021 at 9:21 PM Diego Iastrubni wrote:
> Ori,
>
> You are not welcome here. Please unsubscribe.
>
> Admins -
"Available" output seems weird, or I'm missing something?
Any ideas?
TIA, Vitaly
free -m
totalusedfree shared buff/cache
available
Mem: 31654 29883 937 1 832
27675
Swap: 0 0 0
Omer, thank you!
Is it related to the "Inactive" count from /proc/meminfo?
I used to think that available=free+cache+buffers...
On Tue, May 4, 2021 at 1:19 PM Omer Zak wrote:
> From man free:
>
> available
> Estimation of how much memory is available for starting
> new
>From man free:
available
Estimation of how much memory is available for starting
new applications, without swapping. Unlike the data provided by
the cache or free fields, this field takes into account
page cache and also that not all reclaimable memory slabs will
Note that Linux tries to use available memory for cache, that is why free
memory seems small.
--
Ori Idan CEO Helicon Books
http://www.heliconbooks.com
On Tue, May 4, 2021 at 2:48 PM linux.il wrote:
> Omer, thank you!
> Is it related to the "Inactive" count from /proc/meminfo?
> I used to
Hi,
I'm struggling to get what could mean this odd "The transport type is not
indicated or the error is not transport related" error inside nvme error-log
which is filling my error log.
I also get smart warning of increasing num_err_log_entries , it look like it
could correspond to one error
