Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
I set up a software raid system using mdadm rather than raidtools. I'm not particularly facile with either toolset, so I decided to be progressive. So here's my stupid question. I now have two nice new Dell PowerEdge 2650's running software raid using mdadm. How do I tell, short of popping a disk out, that all is well and good? I have in fact popped disks out. That's how I cloned the second machine. But this is not what I want to do when the machines are in full production. `mdadm -D` seems to be the ticket, but I'm not entirely sure how to interpret the output. E.g. does "State : dirty, no errors" mean all is well in the world? Considering the brutality with which I'm treating these arrays, linux software raid appears remarkably robust.. -- Ron Peterson -o) 87 Taylor Street /\\ Granby, MA 01033 _\_v https://www.yellowbank.com/ ---- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20030819/6436ae39/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |