Your message dated Wed, 18 Feb 2015 14:17:36 -0500
with message-id <[email protected]>
and subject line Re: Bug#778697: libparted2: error on opening with regard to
RAID member devices
has caused the Debian Bug report #778697,
regarding libparted2: error on opening with regard to RAID member devices
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
778697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778697
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libparted2
Severity: grave
With a 'fake RAID' RAID0 device constructed using motherboard firmware,
which has a GPT partitioning table setup using fdisk (gparted failed me
- see #778683), opening gparted now results in errors in relation to the
RAID member disks.
Specifically, I firstly get the following error regarding the first disk
in the RAID array:
Title: Libparted bug found!
Message: Invalid argument during seek for read on /dev/sdb
Clicking on 'ignore' then results in this followup message:
Title: Libparted bug found!
Message: The backup GPT table is corrupt, but the primary appears OK, so
that will be used.
fdisk seems perfectly happy with the setup. Presumably libparted is not
processing the member disks as actually being part of an array.
Marking as grave on the off chance of data loss with libparted not
processing things properly here, and the possibility of users fiddling
with things in gparted in relation to it (e.g. trying to correct the
'unrecognised partition table' status of member disks, wiping out their
array.
Should array members even be listed in gparted?
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/18/2015 1:34 PM, jnqnfe wrote:
> These errors actually disappeared after a reboot :/ ...
>
> I guess that means I should have refreshed something, or fdisk
> should have refreshed something, and thus this can be closed?
I suppose if you can't reproduce it then yes, we'll close it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJU5OVQAAoJENRVrw2cjl5RxjwH/16KndhLju1D6KSdXK46YMlf
fv5dYuUIMgWvDKgfPOSJt7+gBi3N/ejMDc4VxSTpV5W0m/UBvArdEelJJm2XT4bB
0UjGqoHF5lBkfr7yq1KsiyzzCSo0m70DscSCnlahMjV1h8gtICkcDSaktSZhyhQQ
9/d+QA/EyGUrBrRdnPR+rZQPRLPvqCEsBBReG/dBTmYi68k3KMliSEid0XYHBwKA
0Ib9bDynkHs72EvU9zsNTfhLGyQhO+Jjy7y7UrjwrqzEM6AaKaDsLEYfg6CSMwSI
awBf3tgTQ5/PER7RGFOgMtUOJ+Wwv/tSQSjDfetHit9M5+N1msfD+qTIPpTv8kM=
=f0pn
-----END PGP SIGNATURE-----
--- End Message ---
