On Jan 3, 2014, at 4:25 PM, Jim Salter <j...@jrs-s.net> wrote: > > One thing that concerns me is that edits made directly to grub.cfg will get > wiped out with every kernel upgrade when update-grub is run - any idea where > I'd put this in /etc/grub.d to have a persistent change?
/etc/default/grub I don't recommend making it persistent. At this stage of development, a disk failure should cause mount failure so you're alerted to the problem. > I have to tell you, I'm not real thrilled with this behavior either way - it > means I can't have the option to automatically mount degraded filesystems > without the filesystems in question ALWAYS showing as being mounted degraded, > whether the disks are all present and working fine or not. That's kind of > blecchy. =\ If you need something that comes up degraded automatically by design as a supported use case, use md (or possibly LVM which uses different user space tools and monitoring but uses the md kernel driver code and supports raid 0,1,5,6 - quite nifty). I haven't tried this yet, but I think that's also supported with the thin provisioning work, which even if you don't use thin provisioning gets you the significantly more efficient snapshot behavior. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
