I was just asked if I was willing to sell my Stack Overflow account.
Of course, I won't agree to do this, but I was just wondering if there is any official rule regarding this. Do you guys pretty much hand off our accounts to us for us to do with them as we please? Or is there an official guid...
Mine update themselves once in a while. The kernel modules and SPL anyway. Pool itself... I think I'm deliberately running an older version because I'm stupid and paranoid
> If you are running Ubuntu vivid (15.04), you can easily switch between upstart and systemd at will since both packages are installed at present. As of March 9 2015, vivid was changed to use systemd by default, before that upstart was the default.
Traditional VPS cloud platforms have storage, RAM, and compute resources bundled and are best for more predictable workloads, but are much less complicated to work with.
> root@qasdf-servage:/home/qasdfdsaq/ddrescue# cat ddrescue.sh #!/bin/bash DATE=$(date +%Y-%m-%d\.%H%M) ls -1 /dev/disk/by-id/ | grep ata- | grep -v part | while read -r line; do smartctl -x /dev/disk/by-id/$line | tee "/home/qasdfdsaq/smartctl/smartctl ${line:4} ddrescue-start $DATE.txt"; done
ls -1 /dev/disk/by-id/ | grep ata- | grep -v part | while read -r line do ddrescue -B -d -v -f /dev/disk/by-id/$line /dev/null ~qasdfdsaq/ddrescue/ddrescue-$line-$DATE.txt & done
ls -1 /dev/disk/by-id/ | grep ata- | grep -v part | while read -r line; do smartctl -x /dev/disk/by-id/$line | tee "/hom…
Lol. I use my maintenance scripts so infrequently that I have to read the contents every single time to figure out which script it is and to make sure it does what I think it does
The above is my surface-scan script, I used to run it weekly and had a nice colourful spreadsheet to track any changes in my drives' health metrics over time.
Lately I've seen several websites with large ASCII art headers in their HTML. I don't get the point and it seems like this must just be a fad. For instance, tumblr.com has it:
<!--
. .o8 oooo
.o8 "888 `888
...
Showed clearly how many retries each drive needed to read through for example, and any slow sectors, yadda yadda. But these new drives have been so reliable none of them have had a single bad sector in the several years I've had them. So I end up only running the check once or twice a year.
And like chmod, and rm, you definitely don't want an extra -r in there when accidentally destroying the wrong thing
Eh, I virtually never type zfs destroy into a console
(Another benefit of having automatic snapshot management is that you never have to at all... you can even remove the ability to use the command if you so desire)
Y'know that'd be a cool idea. Remove the ability to use the zfs destroy command from your user, and instead, make it so the only way to destroy filesystems is to write the name of the filesystem into a text file somewhere, and have a cron job that runs daily to check the file and then schedule a destroy 24 hours later
The cron job can also email you/all admins on a system and/or delay the action pending the uploading of a certified sobriety test
Only once all the above conditions are satisfied, plus a cryptographically secure authentication code from a secondary authorizer is provided, will the actual delete go ahead.
Cause to be fair, the "nuclear option" on your data needs to have all the same safeguards as an actual nuclear bomb launch IRL.
Eh. By mrain has clearly gone wonky. I should go to bed. G'night @Bob
Also, @allquixotic, ^ may be worth reading. Ubuntu is insulated from that (because they have zfs-native) but if you ever decide to fiddle with debian & ZFS ... make sure you have the right SPL version :\
such a massive waste of time...
maybe I should go ahead and set up that recovery environment on the flash drive :\