Mailinglist Archive: opensuse-bugs (15092 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=304657#c19





--- Comment #19 from Richard Creighton <rccj@xxxxxxxxxxx>  2007-09-14 10:57:35 MST ---
(In reply to comment #12 from Jiri Suchomel)
> > This screenshot is VERY interesting because it
> > shows that it knew about MD1 and MD3 but immediately it also shows that it
> > intended to do file system checks on sda1 and sdb2 among others which are NOT
> > part of the installed Beta 3 system if you will refer to the PartTbl10.3.png. 
> > Those devices are part of the 10.2 file system shown also in Partn10.2.png.
> 
> How is that possible? PartTbl10.3.png shows that sdb1 is used by md1, sdb2 by
> md0 etc. Thomas: Storage::GetTargetMap reports that /dev/sdb2 in devices list
> of /dev/md0:
> 
It took me a bit to understand the question, sorry.   SDAx is part of the IDE
drive which is part of the 10.2 system which should not be being subject to the
repair/test.  SDB to SDE are part of MD0 to MD3 which contain the actual
filesystems.  The SDB-E are only partition/disks which themselves do not
contain a filesystem of anykind and should not have fsck run against them as it
will always fail.   The partition table clearly states that these devices are
part of MDRaid devices and not regular EXT2/3 or FAT or other normal type of
file systems that can be checked by some variant of FSCK.  Thus, the attempt to
run fsck /dev/sdbN I feel is part of the problem as there certainly would be
nothing to repair.   Anything repairable would be withing the filesystem
contained in MD1 or 2 for instance, and that was never checked at any time, nor
was it offerd to be checked.   If I understand your question, that is what I
was trying to point out by the comment #12 above.  


-- 
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.