Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #233353
| From | Gary Dale <gary@extremeground.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: mdadm and whole disk array members |
| Date | 2021-03-23 00:50 +0100 |
| Message-ID | <BVCt4-Sz-5@gated-at.bofh.it> (permalink) |
| References | <BVBdE-d4-7@gated-at.bofh.it> <BVBGH-nf-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2021-03-22 18:49, Andy Smith wrote: > Hi Gary, > > On Mon, Mar 22, 2021 at 06:20:56PM -0400, Gary Dale wrote: >> I suggest that, since it appears the developers can't get this work >> reliably, that the option to use the whole disk be removed and mdadm insist >> on using partitions. At the very least, mdadm --create should issue a >> warning that using a whole device instead of a partition may create >> problems. > I've been using whole disks in mdadm arrays for more than 15 years > across many many servers on Debian stable and have never experienced > what you describe. There must be something else at play here. > > I suggest you post a detailed description of your problem to the > linux-raid mailing list and hopefully someone can help debug it. > > https://raid.wiki.kernel.org/index.php/Linux_Raid#Mailing_list > > Cheers, > Andy > It's not just me but a lot of other people have been having the same problem. It's been reported many times as I discovered after trying to use whole disks. Moreover, the fixes that I'd used in the past don't seem to work reliably without partitions. There doesn't seem to be a downside to using partitions considering that partition tables have never taken up any significant amount of space. It was an interesting experiment / learning experience but I've decided that it's not worth going further so I'm going back to using disks with a single partition.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-22 23:30 +0100
Re: mdadm and whole disk array members Andy Smith <andy@strugglers.net> - 2021-03-23 00:00 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-23 00:50 +0100
Re: mdadm and whole disk array members deloptes <deloptes@gmail.com> - 2021-03-23 13:40 +0100
Re: mdadm and whole disk array members deloptes <deloptes@gmail.com> - 2021-03-23 13:50 +0100
Re: mdadm and whole disk array members Reco <recoverym4n@enotuniq.net> - 2021-03-23 16:50 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 02:30 +0100
Re: mdadm and whole disk array members Felix Miata <mrmazda@earthlink.net> - 2021-03-26 05:10 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 19:10 +0100
Re: mdadm and whole disk array members deloptes <deloptes@gmail.com> - 2021-03-26 08:00 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 19:20 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 02:20 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 02:30 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 02:20 +0100
Re: mdadm and whole disk array members Andy Smith <andy@strugglers.net> - 2021-03-26 17:30 +0100
Re: mdadm and whole disk array members Gary Dale <gary@extremeground.com> - 2021-03-26 19:40 +0100
Re: mdadm and whole disk array members Andy Smith <andy@strugglers.net> - 2021-03-26 22:00 +0100
csiph-web