Quoting Aleksandr Levchuk (alevc...@gmail.com):
Dear Debian Development Community,
What is current status of my bug report of the os-prober related data
corruption?
It's still considered to be a blocker for a new D-I.
...and nobody came up with a solution.
I still consider that a
Dear Debian Development Community,
What is current status of my bug report of the os-prober related data
corruption?
Alex
On Mon, Oct 18, 2010 at 10:08 PM, Christian PERRIER
christ...@perrier.eu.org wrote:
Quoting Aleksandr Levchuk (alevc...@gmail.com):
Dear Christian,
So will this bug be
Quoting Aleksandr Levchuk (alevc...@gmail.com):
Dear Christian,
So will this bug be raised to RC severity?
My previous comment still stands. I'd like people more involved in
grub to comment.
Sigh. From what I've witnessed over the years, os-prober has always
been designed as a component
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
I was upgrading the host space1 and the data corruption occurred on space2. An
install script of os-prober tried mounting as read-only a SAN volume which was
already
Quoting Aleksandr Levchuk (alevc...@cs.ucr.edu):
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
Sigh. From what I've witnessed over the years, os-prober has always
been designed as a component of Debian
Quoting Christian PERRIER (bubu...@debian.org):
Quoting Aleksandr Levchuk (alevc...@cs.ucr.edu):
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
Sigh. From what I've witnessed over the years, os-prober
6 matches
Mail list logo