Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Anthony Sheetz
On Mon, Apr 15, 2013 at 9:29 AM, Ian Campbell wrote: > On Mon, 2013-04-15 at 09:21 -0400, Anthony Sheetz wrote: > > > > > How did you do this? IIRC getting mount options to the root > > filesystem > > to take effect involves more than just editing fstab > > (rootfl

Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Ian Campbell
On Mon, 2013-04-15 at 09:21 -0400, Anthony Sheetz wrote: > > How did you do this? IIRC getting mount options to the root > filesystem > to take effect involves more than just editing fstab > (rootflags= on > command line I think? No idea how one ins

Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Anthony Sheetz
Replies in line. On Mon, Apr 15, 2013 at 9:09 AM, Ian Campbell wrote: > On Mon, 2013-04-15 at 08:19 -0400, Anthony Sheetz wrote: > > > > Did you ever happen to try a transfer over a > > non-tunnelled connection? > > > > > > Yes, tried file transfers from another machine on the loc

Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Ian Campbell
On Mon, 2013-04-15 at 08:19 -0400, Anthony Sheetz wrote: > Did you ever happen to try a transfer over a > non-tunnelled connection? > > > Yes, tried file transfers from another machine on the local network - > never had a problem with those. So this issue isn't the tunnel, goo

Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Anthony Sheetz
Replies in line below. On Mon, Apr 15, 2013 at 4:54 AM, Ian Campbell wrote: > On Wed, 2013-04-10 at 08:17 -0400, Anthony Sheetz wrote: > > Steps to reproduce: > > Install Debian Testing from Netinstall CD, amd64. > > Choose LVM and Full Disk Encryption, with a separate /home > > Resize /home to

Bug#705124: base: Filesystem corruption issue

2013-04-15 Thread Ian Campbell
On Wed, 2013-04-10 at 08:17 -0400, Anthony Sheetz wrote: > Steps to reproduce: > Install Debian Testing from Netinstall CD, amd64. > Choose LVM and Full Disk Encryption, with a separate /home > Resize /home to be 80GB > Install openswan, connect to remote network > Install xen > Set up a virtual ma

Bug#705124: [Pkg-xen-devel] Bug#705124: base: Filesystem corruption issue

2013-04-13 Thread Ben Hutchings
On Sat, 2013-04-13 at 12:30 -0400, Anthony Sheetz wrote: > Alas, I do not have the Thinkpad any more - had to return it. I've > since had to install Debian Stable on the ASUS. Output of lspci and > dmidecode are from that version - fair warning. [...] That doesn't matter - these commands should be

Bug#705124: [Pkg-xen-devel] Bug#705124: base: Filesystem corruption issue

2013-04-13 Thread Anthony Sheetz
Alas, I do not have the Thinkpad any more - had to return it. I've since had to install Debian Stable on the ASUS. Output of lspci and dmidecode are from that version - fair warning. demidecode output is attached. lspci from the Asus: 00:00.0 Host bridge: Intel Corporation Device 0154 (rev 09) 00:

Bug#705124: [Pkg-xen-devel] Bug#705124: base: Filesystem corruption issue

2013-04-12 Thread Thomas Goirand
On 04/10/2013 09:57 PM, Holger Levsen wrote: >> Dear Maintainer, > >> We have discovered a bug which results in corrupted logical volumes, > >> causing xen virtual machines to be unable to boot. > >> We have experienced this bug on two different laptops - Lenovo Thinkpad > >> T430, Asus G55V H

Processed: Re: Bug#705124: base: Filesystem corruption issue

2013-04-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 705124 xen Bug #705124 [base] base: Filesystem corruption issue Bug reassigned from package 'base' to 'xen'. Ignoring request to alter found versions of bug #705124 to the same values previously set Ignoring request to alter fixed versio

Bug#705124: base: Filesystem corruption issue

2013-04-10 Thread Anthony Sheetz
Package: base Severity: critical Tags: lfs Justification: breaks the whole system Dear Maintainer, We have discovered a bug which results in corrupted logical volumes, causing xen virtual machines to be unable to boot. We have experienced this bug on two different laptops - Lenovo Thinkpad T430,