search for: wearleveling

...errors happen before the segfault, suggesting that some memory corruption is underway. AFAICS a pure python plugin should not be able to cause memory corruption. Examples of nbdkit logs for running "make check" or subsets of it from nbd against nbdkit: nbdkit -n -f python script=ssd-ftl-wearleveling.py disksize=52428800 nbdkit: python[6]: error: ssd-ftl-wearleveling.py: callback failed: close nbdkit: python[7]: error: invalid flush request: expecting offset and length == 0 nbdkit: python[7]: error: write reply: Connection reset by peer Segmentation fault nbdkit -n -f python script=ssd-ftl-wea...

...nbdkit shouldn't segfault ever. > > Did you get a stack trace from C (not from Python)? The core files were useless, but I ran nbdkit in gdb and got something... (gdb) run -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 Starting program: /software/nbdkit/src/nbdkit -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 [Thread debugging using libthread_db enabled] Using host libthread_db library &quot...

...segfault ever. >> >> Did you get a stack trace from C (not from Python)? > The core files were useless, but I ran nbdkit in gdb and got something... > > (gdb) run -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 > Starting program: /software/nbdkit/src/nbdkit -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 > [Thread debugging using libthread_db enabled] > Using host libthread_d...

...lugin should not cause memory corruption, and nbdkit shouldn't segfault ever. Did you get a stack trace from C (not from Python)? Rich. > Examples of nbdkit logs for running "make check" or subsets of it from > nbd against nbdkit: > > nbdkit -n -f python script=ssd-ftl-wearleveling.py disksize=52428800 > nbdkit: python[6]: error: ssd-ftl-wearleveling.py: callback failed: close > nbdkit: python[7]: error: invalid flush request: expecting offset and > length == 0 > nbdkit: python[7]: error: write reply: Connection reset by peer > Segmentation fault > > nbd...

...do NOT read-scan remainder of disk. > If Selective self-test is pending on power-up, resume after 0 minute delay. Hmm, lets do some math: 17394 hours "on"-time equals 724.7 days (at continous "on"). 6894 GiB written at 120 GiB drive sizes gives 57.4 Drive-Writes (at optimal wearleveling every cell would have been written 57-58 times) The used Sandforce controller (likly a SF-2281) is not the best at wearleveling, so the "use"-count per cell will be most likely more than double that. For my personal use I would replace that Drive asap. - There is no warranty for it any...

...>> If Selective self-test is pending on power-up, resume after 0 minute >> delay. > > Hmm, lets do some math: > 17394 hours "on"-time equals 724.7 days (at continous "on"). > 6894 GiB written at 120 GiB drive sizes gives 57.4 Drive-Writes > (at optimal wearleveling every cell would have been written 57-58 times) > > The used Sandforce controller (likly a SF-2281) is not the best at > wearleveling, so the "use"-count per cell will be most likely more > than double that. > > For my personal use I would replace that Drive asap. >...

Hi, On Mon, 2016-10-24 at 12:07 +0200, Alessandro Baggi wrote: > === START OF READ SMART DATA SECTION === > SMART Error Log not supported I reckon there's a <snip> between those lines. The line right after the first should read something like: SMART overall-health self-assessment test result: PASSED or "FAILED" for that matter. If not try running smartctl -t short