Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Tom Metro wrote: > I must be missing something simple and obvious here...after creating a > software RAID5 array, I guess you didn't follow some of the links from Monday about why RAID5 is evil ;-) http://www.miracleas.com/BAARF/RAID5_versus_RAID10.txt > Note that the system currently has a RAID1 array with the same type of > file system (XFS) that works fine, suggesting that the file system tools > and mount are behaving normally - or at least were when that file system > was setup (the XFS tools may have since been updated). The system in > question is running Ubuntu Edgy (kernel version 2.6.20-5), so it is > possible that there is an actual bug somewhere. > > The one red flag I'm seeing is: > > # xfs_check /dev/video_vg/video_lv > bad format 0 for inode 130 type 0 > bad magic number 0 for inode 144 > bad magic number 0 for inode 145 > allocated inode 130 has 0 link count > > which is not what I'd expect for a brand new, never mounted file system. > Running xfs_repair crashes: Do other filesystem types work? What about creating an LV on top of a RAID1 device? Matt -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |