Hi all, I am looking at http://bugs.debian.org/251898 and wondering whether it is save to use --assume-clean (which prevents the initial resync) when creating RAID arrays from the Debian installer. Please also see the following discussion on IRC: < madduck> yeah, i am not sure --assume-clean is a good idea. < peterS> madduck: why not? I've tried to think of a reason it would fail for months, and so far I'm too stupid to think of one < madduck> even then < madduck> peterS: because it then assumes that it < madduck> it's clean, period. < peterS> yeah, so? < peterS> the blocks you have not written will have unreliable contents < madduck> in reality, the three components are not properly XORed < peterS> but why would you care about that? < madduck> hm. kinda true. < peterS> the blocks you _do_ write will be correct < peterS> even an uninitialised raid5 or raid6 seems like it would work perfectly well with --assume-clean Do you have any thoughts on the issue? If Debian were to --create its arrays with --assume-clean just before slapping a filesystem on them and installing the system, do you see any potential problems? -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck spamtraps: madduck.bogus@xxxxxxxxxxx "sometimes we sit and read other people's interpretations of our lyrics and think, 'hey, that's pretty good.' if we liked it, we would keep our mouths shut and just accept the credit as if it was what we meant all along." -- john lennon
Attachment:
signature.asc
Description: Digital signature (GPG/PGP)
