Activity log for bug #77470

Date Who What changed Old value New value Message
2006-12-30 04:22:52 Michael Milligan bug added bug
2007-02-16 09:21:15 Colin Watson base-installer: statusexplanation
2008-12-23 02:39:43 Gaetan Nadon mdcfg: status New Invalid
2008-12-23 02:39:43 Gaetan Nadon mdcfg: statusexplanation Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use. BugSquad
2009-01-27 22:49:18 Colin Watson mdcfg: status Invalid Triaged
2009-01-27 22:49:18 Colin Watson mdcfg: importance Undecided Wishlist
2009-01-27 22:49:18 Colin Watson mdcfg: statusexplanation Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use. BugSquad Gaetan: Why isn't this a bug? I don't think it's a good idea to select exactly those bugs for closing where the submitter clearly put effort into producing a well-thought-out proposal. Please stop doing this. I notice that the mdadm(8) manual page says: --assume-clean Tell mdadm that the array pre-existed and is known to be clean. It can be useful when trying to recover from a major failure as you can be sure that no data will be affected unless you actually write to the array. It can also be used when creating a RAID1 or RAID10 if you want to avoid the initial resync, however this practice -- while normally safe -- is not recommended. Use this only if you really know what you are doing. Thus I rather feel we shouldn't do this by default. A chunk size prompt seems reasonable, perhaps only in expert mode.