https://bugzilla.novell.com/show_bug.cgi?id=371657
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371657#c38
Kay Sievers changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kasievers@novell.com
AssignedTo|kasievers@novell.com |bnc-team-screening@forge.provo.novell.com
Component|Kernel |YaST2
QAContact|qa@suse.de |jsrain@novell.com
--- Comment #38 from Kay Sievers 2008-11-17 18:07:08 MST ---
Yeah, but the problem is that none of the things which access the partitions
read the partition type value, and should still continue to open the device,
and cause the "access beyond end of device" errors. I still have no idea why
the messages disappear.
But if it helps to change the partition type, let's see if the partitioner can
do something. Reassigning to Yast.
Summary: dmraid setups create kernel partitions which are completely invalid,
and cause "access beyond end of device" errors on probing for metadata.
Dean, the bug reporter, sees that setting a different partition type in the
partition table makes the bug disappear.
This may be not a sufficient fix for the general problem with dmraid setups,
but if it helps, please look if we can do something here. Details in
comment#37.
--
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.