Mailinglist Archive: opensuse-bugs (7823 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=463829

User pgnet.trash@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=463829#c64





--- Comment #64 from pgnet _ <pgnet.trash@xxxxxxxxx>  2009-02-26 08:29:50 MST 
---
(In reply to comment #63)
> Yes, no iommu parameter necessary.

thanks for clarifying.

> Can you please keep it running for a few
> days and see whether anything explodes?

that's going to be a challenge if not in xen ...

overnight (but of course, not 'using' the drives) is doable.

since yesterday, the two 'new' raid arrays have been 'RESYNCING' (that sure
takes awhile!).  /dev/md5 is 100% done; md4 is 74% done, atm.  afaict, no
errors.

>  I'm a bit worried because you
> previously reported lvm didn't work even with the patched kernel.

as am i. however, since earlier tests, i've:

-- ensured i 'pvremove -ff' before 'pvcreate'.  i've found that simply
reformatting doesn't always (that's what's confusing ... seems to depend on
where i stop/restart the manual procedures) clear all the info off the drive. 
if there's an errant pv around, that'll cause problems.

-- made sure to _manually_ add the new raid arrays' UUIDs to mdadm.conf. 
"Partitioner" seems to do it automatically, but manually creating the arrays
does not.  without the mod, the raid arrays don't start and the lvms on the
raid arrays are never recognized.

i'm not sure whether there's a step in the manual process (mdadm ... ?) that
_should_ do the mdadm.conf mods. :-/

> Thanks.

you too.  this has been a long thread -- not much help from me.  your help's
appreciated.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.