Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #276320

Re: new computer arriving soon

From George at Clug <Clug@goproject.info>
Newsgroups linux.debian.user
Subject Re: new computer arriving soon
Date 2025-01-03 00:40 +0100
Message-ID <K0CXf-56Dc-3@gated-at.bofh.it> (permalink)
References <K0Ckx-56az-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Friday, 03-01-2025 at 09:57 Michael Stone wrote:
> On Thu, Jan 02, 2025 at 06:29:08PM +1100, George at Clug wrote:
> >I once used/tested with RAID 6 and was amazed how long it took to rebuild a 3TB swapped hard drive (about 8 hours, if I recall).

(This was using an Intel 8 port SAS/SATA card, sadly I cannot get Battery Backup for it anymore, and running without battery backup is not worthwhile).


> 
> Spinning disks are slow; 8 hours for 3TB is about 100MB/s and 8h is 
> about how much time I'd expect it to take to write a commodity disk that 
> size. It becomes really painful on a 24TB drive (8 times as large, 8 
> times as long; 

 24TB drive - WOW - just thinking about that hurts.

> a fast spinning disk might be able to cut that down to a 
> full day). If you want significant speed increases you need an nvme
> drive--but beware: there's a default rate-limit to minimize impact to 
> other work. (see /proc/sys/dev/raid/speed_limit_max, probably 200MB/s, 
> and you'd want to set it much higher to fully utilize nvme storage.) 

I assume speed_limit* is for mdadm ?  When I get time, I would like to do some testing with mdadm. I think I did one test run about 10 or 15 years ago, but now I just work (er play) with Desktop computers where single drives and rsync backups is sufficient for my needs. I am too lazy for my own good, I guess.

I think one issue with RAID is, most people do not keep watch on drive health, and it is only when the second drive fails and the whole RAID dies, that they notice there were issues long ago. (maybe that is just me?)

Does anyone have experience with mdadm and for keeping an eye of the health of your drives and RAID?  I am curious if you get timely notifications that a drive is not well (starting to get too many errors) and should be replaced, so you can replace the drive before failure?

I get yearly power outages due to storms, though I do have UPS, sometimes they loose power before clean shutdown. I need to pay more attention to battery health and do testing, which I do not do, my fault. My recommendation to people 1) if you use UPS, test by putting your severs into read-only mode, then remove power and see if the system automatically powers down before the batteries fail. 2) if you do backups, occasionally try to do a full disaster restore from backups. 

I wonder how well mdadm survives unexpected power outages (or lockups)?

Having had worked with Microsoft Operating systems, I was quite concerned about the possibility of lockups when I started working with Linux servers around 2009. As I think about it now, I have never had a lockup on a Linux server. And this very much holds true for my home KVM hypervisors and servers that I test with. The KVM hypervisors run 24x7 for about the past 15 years and have never locked up. Amazing and pleasing. 

Some reading for me:
https://www.cyberciti.biz/tips/linux-raid-increase-resync-rebuild-speed.html
The /proc/sys/dev/raid/speed_limit_max is config file that reflects the current “goal” rebuild speed for times when no non-rebuild activity is current on an array. The default is 100,000.

https://tldp.org/HOWTO/Software-RAID-HOWTO-6.html
6.5 Monitoring RAID arrays 

https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_storage_devices/managing-raid_managing-storage-devices#setting-up-email-notifications-to-monitor-a-raid_managing-raid
21.18. Setting up email notifications to monitor a RAID

https://medium.com/@kahalekar.sunil/how-to-configure-raid-and-monitor-disk-usage-ensuring-timely-notification-via-email-in-case-of-facf4c4d7656

https://www.ionos.com/help/server-cloud-infrastructure/dedicated-server-for-servers-purchased-before-102818/rescue-and-recovery/software-raid-status-monitoring-linux/


George.

> 
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-21 18:50 +0100
  Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-21 20:30 +0100
    Re: new computer arriving soon Joe <joe@jretrading.com> - 2024-12-21 21:20 +0100
      Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:20 +0100
    Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:20 +0100
      UEFI, Export from Virtualbox [WAS Re: new computer arriving soon] "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-22 09:50 +0100
      Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-26 20:40 +0100
        Re: new computer arriving soon David Christensen <dpchrist@holgerdanske.com> - 2024-12-26 23:40 +0100
          Re: new computer arriving soon David Wright <deblis@lionunicorn.co.uk> - 2024-12-27 17:30 +0100
            Re: new computer arriving soon Marc Shapiro <marcnshap@gmail.com> - 2024-12-31 05:10 +0100
              Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2024-12-31 05:40 +0100
                Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-31 19:00 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2024-12-31 23:00 +0100
                Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-01 00:00 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 01:00 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-01 15:00 +0100
                Re: new computer arriving soon Frank Guthausen <fg.debian@shimps.de> - 2025-01-01 15:30 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-01 15:40 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 16:40 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-01 17:20 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 18:00 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-01 18:00 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 03:10 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-02 03:40 +0100
                Re: new computer arriving soon Charles Curley <charlescurley@charlescurley.com> - 2025-01-01 17:30 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 18:20 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 22:00 +0100
                Re: new computer arriving soon Joe <joe@jretrading.com> - 2025-01-01 19:50 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 22:50 +0100
                Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-02 14:50 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-03 04:00 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-03 17:30 +0100
                Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-03 13:10 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 03:30 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-02 03:40 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:30 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-02 04:50 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 16:40 +0100
                Re: new computer arriving soon pocket@homemail.com - 2025-01-02 17:10 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-04 05:00 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-04 11:20 +0100
                Gene and networkmanager (was: Re: new computer arriving soon) Max Nikulin <manikulin@gmail.com> - 2025-01-05 04:50 +0100
                Re: Gene and networkmanager (was: Re: new computer arriving soon) gene heskett <gheskett@shentel.net> - 2025-01-05 17:20 +0100
                /dev/serial/by-id (was: Re: new computer arriving soon) Max Nikulin <manikulin@gmail.com> - 2025-01-05 05:00 +0100
                Re: /dev/serial/by-id (was: Re: new computer arriving soon) gene heskett <gheskett@shentel.net> - 2025-01-05 17:30 +0100
                Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-06 03:30 +0100
                Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-06 08:20 +0100
                Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-07 04:20 +0100
                Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-07 10:00 +0100
                Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-07 14:50 +0100
                Mass storage sizes (was: /dev/serial/by-id) Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 16:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-07 16:50 +0100
                Re: Mass storage sizes eben@gmx.us - 2025-01-07 17:10 +0100
                Re: Mass storage sizes <tomas@tuxteam.de> - 2025-01-07 17:40 +0100
                Re: Mass storage sizes eben@gmx.us - 2025-01-07 18:00 +0100
                Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 20:40 +0100
                Re: Mass storage sizes <tomas@tuxteam.de> - 2025-01-08 06:30 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-07 17:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-07 17:30 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-07 18:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Nicholas Geovanis <nickgeovanis@gmail.com> - 2025-01-09 04:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-09 05:50 +0100
                Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-09 16:30 +0100
                Re: Mass storage sizes Dan Purgert <dan@djph.net> - 2025-01-09 18:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Nicolas George <george@nsup.org> - 2025-01-09 21:50 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-10 00:50 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Jeffrey Walton <noloader@gmail.com> - 2025-01-10 01:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2025-01-10 02:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-10 11:00 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) gene heskett <gheskett@shentel.net> - 2025-01-10 15:10 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) <tomas@tuxteam.de> - 2025-01-10 07:30 +0100
                Re: Mass storage sizes John Hasler <john@sugarbit.com> - 2025-01-10 15:50 +0100
                Re: Mass storage sizes eben@gmx.us - 2025-01-10 21:40 +0100
                Re: Mass storage sizes gene heskett <gheskett@shentel.net> - 2025-01-11 01:50 +0100
                Re: Mass storage sizes Jeffrey Walton <noloader@gmail.com> - 2025-01-11 01:40 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Heriberto Avelino <heriberto.avelino@gmail.com> - 2025-01-10 01:30 +0100
                Re: Mass storage sizes Kushal Kumaran <kushal@locationd.net> - 2025-01-07 20:20 +0100
                Re: Mass storage sizes Nicolas George <george@nsup.org> - 2025-01-07 21:10 +0100
                Re: Mass storage sizes Michael Stone <mstone@debian.org> - 2025-01-07 23:10 +0100
                Re: Mass storage sizes Urs Thuermann <urs@isnogud.escape.de> - 2025-01-10 03:00 +0100
                Re: Mass storage sizes Michael Stone <mstone@debian.org> - 2025-01-10 05:30 +0100
                Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-10 15:40 +0100
                Re: Mass storage sizes Charles Curley <charlescurley@charlescurley.com> - 2025-01-07 23:10 +0100
                Re: Mass storage sizes gene heskett <gheskett@shentel.net> - 2025-01-08 00:30 +0100
                Re: Mass storage sizes "Thomas Schmitt" <scdbackup@gmx.net> - 2025-01-07 17:40 +0100
                Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 20:30 +0100
                Re: Mass storage sizes (was: /dev/serial/by-id) Jeffrey Walton <noloader@gmail.com> - 2025-01-09 08:40 +0100
                Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-08 04:00 +0100
                Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-08 04:10 +0100
                Re: /dev/serial/by-id Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2025-01-07 11:20 +0100
                Specific mdadm instructions for Gene [WAS Re: new computer arriving  soon] "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-02 17:00 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer  arrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-02 23:10 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer  arrivingsoon] Andy Smith <andy@strugglers.net> - 2025-01-02 23:20 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer  arrivingsoon] Nicolas George <george@nsup.org> - 2025-01-02 23:30 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer  arrivingsoon] Michael Stone <mstone@debian.org> - 2025-01-03 00:10 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Jeffrey Walton <noloader@gmail.com> - 2025-01-03 04:00 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new  computerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-03 05:00 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new  computerarrivingsoon] Andy Smith <andy@strugglers.net> - 2025-01-03 14:00 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new computer  arrivingsoon] Max Nikulin <manikulin@gmail.com> - 2025-01-03 03:40 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new  computerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-03 05:10 +0100
                Re: Specific mdadm instructions for Gene [WAS Re: new  computerarrivingsoon] Max Nikulin <manikulin@gmail.com> - 2025-01-04 04:30 +0100
                Re: Specific mdadm instructions for Gene [WAS Re:  newcomputerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-04 04:50 +0100
                sgdisk missing under Armbian for Gene [WAS Specific mdadm  instructions for Gene] "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-03 12:40 +0100
                Re: sgdisk missing under Armbian for Gene [WAS Specific mdadm  instructions for Gene] Nicolas George <george@nsup.org> - 2025-01-03 12:50 +0100
                Re: sgdisk missing under Armbian for Gene [WAS Specific  mdadminstructions for Gene] gene heskett <gheskett@shentel.net> - 2025-01-03 17:40 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:00 +0100
                Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-02 05:30 +0100
                Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-02 08:30 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-02 23:40 +0100
                Re: new computer arriving soon fxkl47BF@protonmail.com - 2025-01-02 23:50 +0100
                Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:00 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 00:20 +0100
                Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:50 +0100
                Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2025-01-03 17:00 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 17:20 +0100
                Re: new computer arriving soon David Wright <deblis@lionunicorn.co.uk> - 2025-01-10 05:50 +0100
                Re: new computer arriving soon Greg Wooledge <greg@wooledge.org> - 2025-01-03 00:10 +0100
                Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:00 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 00:00 +0100
                Re: new computer arriving soon  George at Clug <Clug@goproject.info> - 2025-01-03 00:40 +0100
                Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-03 00:50 +0100
                Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2025-01-03 17:00 +0100
                Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 16:30 +0100
              Re: new computer arriving soon Frank Guthausen <fg.debian@shimps.de> - 2024-12-31 20:20 +0100
              Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:10 +0100
                Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-02 23:50 +0100
                Re: new computer arriving soon Marc Shapiro <marcnshap@gmail.com> - 2025-01-06 06:10 +0100
          Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-27 20:20 +0100
  Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2024-12-22 00:40 +0100
    Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:30 +0100
      Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2024-12-22 05:50 +0100
  Re: new computer arriving soon songbird <songbird@anthive.com> - 2024-12-22 17:20 +0100

csiph-web