laarcnew | comments | discord | tags | ask | show | place | submitlogin

This is exactly what happened in this case. After finding 2 different superblocks, dmraid decided that instead of actually asking the user for what to do, it should prefer one over another (in this case ddf1 over isw).

Furthermore, it again decided to automatically rebuild the array and fix the seemingly inconsistency between array members without consulting the user first.

All it took for my RAID set to become invalid and me losing my data, was booting up Ubuntu Desktop 18.04 ISO image.

The author's self-restraint is impressive. If this happened to me, I would (a) lay the blame squarely on Ubuntu, (b) never use Ubuntu again, (c) point to this every time anyone recommends using Ubuntu for serious work.

This is a specific instance of a general pattern: Stop writing software that tries to be clever. Software shouldn't be clever. It should be predictable. Otherwise you get https://www.forbes.com/sites/taylorarmerding/2018/11/20/hard-questions-raised-when-a-software-glitch-takes-down-an-airliner/#65e32b6a7b1d



2 points by gerikson 492 days ago

> I would (a) lay the blame squarely on Ubuntu

Why Ubuntu? Isn't the problem that the `dmraid` application makes the wrong choices?

-----


Admittedly it's more of an emotional reaction than a logical one. Linux is traditionally for forensics (at least compared to Windows and macOS) so it's unfortunate to hear that a distro wiped someone's data simply by booting into it.

The author wants to file a bug report against dmraid: https://news.ycombinator.com/item?id=19043956

-----




Welcome | Guidelines | Bookmarklet | Feature Requests | Source | Contact | Twitter | Lists

RSS (stories) | RSS (comments)

Search: