Any other ideas on how to move forward with this bug?
On Wed, Apr 17, 2013 at 8:57 AM, Ian Campbell wrote:
> On Tue, 2013-04-16 at 09:39 -0400, Anthony Sheetz wrote:
>>
>> What does dom0 dmesg say about barriers on that
>> device/filesystem?
>
>> Nothing in dmesg about barriers on
On Tue, 2013-04-16 at 09:39 -0400, Anthony Sheetz wrote:
>
> What does dom0 dmesg say about barriers on that
> device/filesystem?
> Nothing in dmesg about barriers on any file system. 'dmesg|grep
> barrier' returns nothing.
I've just realised that the message in domU is from th
On Mon, 2013-04-15 at 15:02 -0400, Anthony Sheetz wrote:
> Current status.
> New laptop hard drive purchased and installed.
Thanks!
> Experiment 1
[]
> Result: 4.9Gb file transferred fine!
> Experiment 2
[...]
> Result: successful transfer.
Great news.
> Experiment 3
> Change from above (2
Current status.
New laptop hard drive purchased and installed.
Experiment 1
Instead of LVM with full disk encryption, have used LVM without full disk
encryption.
Instead of transferring file to the lv used for DomU '/', have created a
new lv mounted with 'mount /dev/xvda3 /mnt' insided DomU to use
4 matches
Mail list logo
