[Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2

2016-09-16 Thread Lenz Grimmer
FWIW, I am currently experiencing the same error when running
"createrepo" on a repo containing 20 RPMs. The host system is running
Ubuntu 14.04.5 LTS, libxml2 version is 2.9.1+dfsg1-3ubuntu. For me, the
error occurs every time, removing the repodata directories does not
resolve this.

 % createrepo .
Spawning worker 0 with 20 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
I/O error : No such file or directory

(process:18005): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag package line 2263


(process:18005): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag filelists line 2

Traceback (most recent call last):
  File "/usr/share/createrepo/genpkgmetadata.py", line 308, in 
main(sys.argv[1:])
  File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main
mdgen.doRepoMetadata()
  File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, in 
doRepoMetadata
rp.getFilelists(complete_path, csum)
  File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 54, in 
getFilelists
self.repoid))
TypeError: Parsing filelists.xml error: Premature end of data in tag file line 
2332

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375637

Title:
  Premature end of data in tag file line 247651 with libxml2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1375637/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415859] Re: Immediate I/O errors when dd-ing data to an external USB3 disk

2015-01-29 Thread Lenz Grimmer
As I wrote in the initial report: "This seems to be a regression in the
mainline Kernel, as the default kernel (3.13.0-44-generic) performed
this dd operation without issues - but it seems to be using a different
USB driver for the disk"

I also included the relevant kernel output.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415859

Title:
  Immediate I/O errors when dd-ing data to an external USB3 disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-29 Thread Lenz Grimmer
Update: using the mainline kernel, I observe a slightly different
pattern. When running multiple heavy I/O operations in parallel (e.g.
rsyncing a large ISO image to a container, performing an http upload
into another one and running "yum update" on all containers), the large
uploads start to stall and come to a crawling halt at some point.

"dmesg" reveals some different btrfs related issues:

[ 6838.005920] INFO: task kworker/u16:0:5815 blocked for more than 120 seconds.
[ 6838.005924]   Not tainted 3.19.0-031900rc6-generic #201501261152
[ 6838.005925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 6838.005926] kworker/u16:0   D 88024422bb18 0  5815  2 0x
[ 6838.005953] Workqueue: events_unbound btrfs_async_reclaim_metadata_space 
[btrfs]
[ 6838.005954]  88024422bb18 88024422bad8 88024422bfd8 
000141c0
[ 6838.005956]  88030c1b0700 88021a1e13a0 8802c78a75c0 
88024422bb08
[ 6838.005958]  88024422bc88 7fff 7fff 
8802c78a75c0
[ 6838.005959] Call Trace:
[ 6838.005965]  [] schedule+0x29/0x70
[ 6838.005968]  [] schedule_timeout+0x1b5/0x210
[ 6838.005972]  [] ? __queue_delayed_work+0xaa/0x1a0
[ 6838.005974]  [] ? try_to_grab_pending+0x4b/0x80
[ 6838.005976]  [] wait_for_completion+0xa7/0x160
[ 6838.005979]  [] ? try_to_wake_up+0x2a0/0x2a0
[ 6838.005983]  [] writeback_inodes_sb_nr+0x86/0xb0
[ 6838.005997]  [] shrink_delalloc+0x10d/0x300 [btrfs]
[ 6838.006011]  [] flush_space+0xd8/0x150 [btrfs]
[ 6838.006022]  [] 
btrfs_async_reclaim_metadata_space+0x14b/0x1d0 [btrfs]
[ 6838.006024]  [] process_one_work+0x14d/0x460
[ 6838.006026]  [] worker_thread+0x11b/0x3f0
[ 6838.006029]  [] ? create_worker+0x1e0/0x1e0
[ 6838.006031]  [] kthread+0xc9/0xe0
[ 6838.006032]  [] ? flush_kthread_worker+0x90/0x90
[ 6838.006035]  [] ret_from_fork+0x7c/0xb0
[ 6838.006037]  [] ? flush_kthread_worker+0x90/0x90
[ 6957.962660] INFO: task kworker/u16:0:5815 blocked for more than 120 seconds.
[ 6957.962667]   Not tainted 3.19.0-031900rc6-generic #201501261152
[ 6957.962668] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 6957.962671] kworker/u16:0   D 88024422bb18 0  5815  2 0x
[ 6957.962706] Workqueue: events_unbound btrfs_async_reclaim_metadata_space 
[btrfs]
[ 6957.962709]  88024422bb18 88024422bad8 88024422bfd8 
000141c0
[ 6957.962713]  88030c1b0700 88021a1e13a0 8802c78a75c0 
88024422bb08
[ 6957.962716]  88024422bc88 7fff 7fff 
8802c78a75c0
[ 6957.962720] Call Trace:
[ 6957.962741]  [] schedule+0x29/0x70
[ 6957.962746]  [] schedule_timeout+0x1b5/0x210
[ 6957.962752]  [] ? __queue_delayed_work+0xaa/0x1a0
[ 6957.962756]  [] ? try_to_grab_pending+0x4b/0x80
[ 6957.962760]  [] wait_for_completion+0xa7/0x160
[ 6957.962765]  [] ? try_to_wake_up+0x2a0/0x2a0
[ 6957.962771]  [] writeback_inodes_sb_nr+0x86/0xb0
[ 6957.962787]  [] shrink_delalloc+0x10d/0x300 [btrfs]
[ 6957.962803]  [] flush_space+0xd8/0x150 [btrfs]
[ 6957.962817]  [] 
btrfs_async_reclaim_metadata_space+0x14b/0x1d0 [btrfs]
[ 6957.962822]  [] process_one_work+0x14d/0x460
[ 6957.962826]  [] worker_thread+0x11b/0x3f0
[ 6957.962830]  [] ? create_worker+0x1e0/0x1e0
[ 6957.962834]  [] kthread+0xc9/0xe0
[ 6957.962838]  [] ? flush_kthread_worker+0x90/0x90
[ 6957.962842]  [] ret_from_fork+0x7c/0xb0
[ 6957.962846]  [] ? flush_kthread_worker+0x90/0x90
[ 6962.761961] systemd-hostnamed[15586]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
[ 7437.789596] INFO: task yum:14547 blocked for more than 120 seconds.
[ 7437.789600]   Not tainted 3.19.0-031900rc6-generic #201501261152
[ 7437.789601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 7437.789602] yum D 880286777868 0 14547  14546 0x
[ 7437.789605]  880286777868 00020001 880286777fd8 
000141c0
[ 7437.789607]  88002e07db00 81c1c500 8801f8892740 
880286777858
[ 7437.789608]  8802867779d8 7fff 7fff 
8801f8892740
[ 7437.789610] Call Trace:
[ 7437.789616]  [] schedule+0x29/0x70
[ 7437.789619]  [] schedule_timeout+0x1b5/0x210
[ 7437.789623]  [] ? __queue_delayed_work+0xaa/0x1a0
[ 7437.789625]  [] ? try_to_grab_pending+0x4b/0x80
[ 7437.789628]  [] wait_for_completion+0xa7/0x160
[ 7437.789634]  [] ? try_to_wake_up+0x2a0/0x2a0
[ 7437.789638]  [] writeback_inodes_sb_nr+0x86/0xb0
[ 7437.789674]  [] shrink_delalloc+0x10d/0x300 [btrfs]
[ 7437.789692]  [] ? get_alloc_profile+0x5d/0x90 [btrfs]
[ 7437.789707]  [] ? btrfs_get_alloc_profile+0x30/0x40 [btrfs]
[ 7437.789719]  [] flush_space+0xd8/0x150 [btrfs]
[ 7437.789731]  [] reserve_metadata_bytes+0x1d9/0x590 [btrfs]
[ 7437.789743]  [] ? btrfs_search_slot+0x3a9/0x870 [btrfs]
[ 7437.789760]  [] ? set_state_bits+0x40/0x80 [btrfs]
[ 7437.789773]  [] btrfs_bl

[Bug 1415859] Re: Immediate I/O errors when dd-ing data to an external USB3 disk

2015-01-29 Thread Lenz Grimmer
I ran "apport-collect 1415859" as requested and changed the status to
"Confirmed" now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415859

Title:
  Immediate I/O errors when dd-ing data to an external USB3 disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415859] Re: Immediate I/O errors when dd-ing data to an external USB3 disk

2015-01-29 Thread Lenz Grimmer
apport information

** Tags added: apport-collected

** Description changed:

  I discovered this bug while trying to dd a potentially corrupt Btrfs
  file system to an external hard disk (see #1415510 for details).
  Unfortunately "ubuntu-bug" refused to file this report, as I'm running
  the mainline kernel (as requested in the other bug report).
  
  I'm running Linux 3.19.0-031900rc6-generic (x86_64) in Ubuntu Trusty on
  an IBM Thinkpad T440. I am using an external 4TB Samsung USB3 hard disk
  drive for backup purposes.
  
  % cat /proc/version 
  Linux version 3.19.0-031900rc6-generic (kernel@gomeisa) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201501261152 SMP Mon Jan 26 16:53:27 UTC 2015
  
  When trying to dd the content of a logical volume into an image file on
  the external disk drive (/dev/sdc1, formatted using ext4), the kernel
  immediately begins to throw I/O Errors:
  
  % sudo dd bs=8k if=/dev/mapper/ubuntu--vg-container
  of=/media/lenz/e2a4dc71-4c96-4dab-982c-29918e556afd/vg-container.img
  
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.321122] usb 2-1: new 
SuperSpeed USB device number 5 using xhci_hcd
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.33] usb 2-1: New USB 
device found, idVendor=04e8, idProduct=6125
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337781] usb 2-1: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337783] usb 2-1: Product: 
D3 Station
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337785] usb 2-1: 
Manufacturer: Samsung 
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337786] usb 2-1: 
SerialNumber: 011E0A49
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352472] usb-storage 
2-1:1.0: USB Mass Storage device detected
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352561] scsi host3: 
usb-storage 2-1:1.0
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352644] usbcore: registered 
new interface driver usb-storage
  Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.354202] usbcore: registered 
new interface driver uas
  Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.349445] scsi 3:0:0:0: 
Direct-Access Samsung  D3 Station   0202 PQ: 0 ANSI: 6
  Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.349740] sd 3:0:0:0: 
Attached scsi generic sg2 type 0
  Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.351547] sd 3:0:0:0: [sdc] 
Spinning up disk...
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  526.766731] ...ready
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.788913] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789457] sd 3:0:0:0: [sdc] 
Write Protect is off
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789459] sd 3:0:0:0: [sdc] 
Mode Sense: 2b 00 10 08
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789992] sd 3:0:0:0: [sdc] 
Write cache: enabled, read cache: enabled, supports DPO and FUA
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.790315] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.813839]  sdc: sdc1
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.814333] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
  Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.843305] sd 3:0:0:0: [sdc] 
Attached SCSI disk
  Jan 29 12:18:23 lenz-ThinkPad-T440 kernel: [  533.145443] EXT4-fs (sdc1): 
mounted filesystem with ordered data mode. Opts: (null)
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192217] sd 3:0:0:0: [sdc] 
FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.19] sd 3:0:0:0: [sdc] 
CDB: 
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192223] Write(10): 2a 00 01 
a7 a4 00 00 3c 00 00
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192230] blk_update_request: 
I/O error, dev sdc, sector 222109696
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192236] EXT4-fs warning 
(device sdc1): ext4_end_bio:317: I/O error -5 writing to inode 13 (offset 
33554432 size 8388608 starting block 27763968)
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192239] Buffer I/O error on 
device sdc1, logical block 27763456
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192242] Buffer I/O error on 
device sdc1, logical block 27763457
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192244] Buffer I/O error on 
device sdc1, logical block 27763458
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192245] Buffer I/O error on 
device sdc1, logical block 27763459
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192247] Buffer I/O error on 
device sdc1, logical block 27763460
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192248] Buffer I/O error on 
device sdc1, logical block 27763461
  Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192

[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-29 Thread Lenz Grimmer
NB: Trying to "dd" an image of the Btrfs file system to an external USB3
disk using the mainline kernel revealed a different issue, which I
reported as bug#1415859.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415859] Re: Immediate I/O errors when dd-ing data to an external USB3 disk

2015-01-29 Thread Lenz Grimmer
** Attachment added: "Output of lsusb -v"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415859/+attachment/4307842/+files/lsusb.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415859

Title:
  Immediate I/O errors when dd-ing data to an external USB3 disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415859] [NEW] Immediate I/O errors when dd-ing data to an external USB3 disk

2015-01-29 Thread Lenz Grimmer
Public bug reported:

I discovered this bug while trying to dd a potentially corrupt Btrfs
file system to an external hard disk (see #1415510 for details).
Unfortunately "ubuntu-bug" refused to file this report, as I'm running
the mainline kernel (as requested in the other bug report).

I'm running Linux 3.19.0-031900rc6-generic (x86_64) in Ubuntu Trusty on
an IBM Thinkpad T440. I am using an external 4TB Samsung USB3 hard disk
drive for backup purposes.

% cat /proc/version 
Linux version 3.19.0-031900rc6-generic (kernel@gomeisa) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201501261152 SMP Mon Jan 26 16:53:27 UTC 2015

When trying to dd the content of a logical volume into an image file on
the external disk drive (/dev/sdc1, formatted using ext4), the kernel
immediately begins to throw I/O Errors:

% sudo dd bs=8k if=/dev/mapper/ubuntu--vg-container
of=/media/lenz/e2a4dc71-4c96-4dab-982c-29918e556afd/vg-container.img

Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.321122] usb 2-1: new 
SuperSpeed USB device number 5 using xhci_hcd
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.33] usb 2-1: New USB 
device found, idVendor=04e8, idProduct=6125
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337781] usb 2-1: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337783] usb 2-1: Product: D3 
Station
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337785] usb 2-1: 
Manufacturer: Samsung 
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.337786] usb 2-1: 
SerialNumber: 011E0A49
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352472] usb-storage 2-1:1.0: 
USB Mass Storage device detected
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352561] scsi host3: 
usb-storage 2-1:1.0
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.352644] usbcore: registered 
new interface driver usb-storage
Jan 29 12:18:10 lenz-ThinkPad-T440 kernel: [  520.354202] usbcore: registered 
new interface driver uas
Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.349445] scsi 3:0:0:0: 
Direct-Access Samsung  D3 Station   0202 PQ: 0 ANSI: 6
Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.349740] sd 3:0:0:0: Attached 
scsi generic sg2 type 0
Jan 29 12:18:11 lenz-ThinkPad-T440 kernel: [  521.351547] sd 3:0:0:0: [sdc] 
Spinning up disk...
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  526.766731] ...ready
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.788913] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789457] sd 3:0:0:0: [sdc] 
Write Protect is off
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789459] sd 3:0:0:0: [sdc] 
Mode Sense: 2b 00 10 08
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.789992] sd 3:0:0:0: [sdc] 
Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.790315] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.813839]  sdc: sdc1
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.814333] sd 3:0:0:0: [sdc] 
976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
Jan 29 12:18:22 lenz-ThinkPad-T440 kernel: [  532.843305] sd 3:0:0:0: [sdc] 
Attached SCSI disk
Jan 29 12:18:23 lenz-ThinkPad-T440 kernel: [  533.145443] EXT4-fs (sdc1): 
mounted filesystem with ordered data mode. Opts: (null)
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192217] sd 3:0:0:0: [sdc] 
FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.19] sd 3:0:0:0: [sdc] 
CDB: 
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192223] Write(10): 2a 00 01 
a7 a4 00 00 3c 00 00
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192230] blk_update_request: 
I/O error, dev sdc, sector 222109696
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192236] EXT4-fs warning 
(device sdc1): ext4_end_bio:317: I/O error -5 writing to inode 13 (offset 
33554432 size 8388608 starting block 27763968)
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192239] Buffer I/O error on 
device sdc1, logical block 27763456
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192242] Buffer I/O error on 
device sdc1, logical block 27763457
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192244] Buffer I/O error on 
device sdc1, logical block 27763458
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192245] Buffer I/O error on 
device sdc1, logical block 27763459
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192247] Buffer I/O error on 
device sdc1, logical block 27763460
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192248] Buffer I/O error on 
device sdc1, logical block 27763461
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192249] Buffer I/O error on 
device sdc1, logical block 27763462
Jan 29 12:18:58 lenz-ThinkPad-T440 kernel: [  568.192251] Buffer I/O error on 
device sdc1, logical bl

[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-29 Thread Lenz Grimmer
Looks like the repair was successful:

% sudo btrfsck --repair /dev/mapper/ubuntu--vg-container
enabling repair mode
Checking filesystem on /dev/mapper/ubuntu--vg-container
UUID: b95b58fb-d0b2-4735-a4ed-2033537eb89a
checking extents
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 37972963086 bytes used err is 0
total csum bytes: 44021104
total tree bytes: 651902976
total fs tree bytes: 470499328
total extent tree bytes: 103186432
btree space waste bytes: 136847949
file data blocks allocated: 126929125376
 referenced 44007616512
Btrfs v3.12


I'll now proceed with testing this against the upstream kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-29 Thread Lenz Grimmer
FYI, I'm now running Kernel version 3.19.0-031900rc6-generic from the
URL you mentioned in #4. Let's see if the issue persists.

The file system mounts fine, but I'm concerned about the output of
btrfsck:

Checking filesystem on /dev/mapper/ubuntu--vg-container
UUID: b95b58fb-d0b2-4735-a4ed-2033537eb89a
checking extents
checking free space cache
free space inode generation (0) did not match free space cache generation 
(135494)
free space inode generation (0) did not match free space cache generation 
(135494)
There is no free space entry for 11902451712-11904450560
There is no free space entry for 11902451712-12914262016
cache appears valid but isnt 11840520192
There is no free space entry for 14083878912-14084898816
There is no free space entry for 14083878912-15061745664
cache appears valid but isnt 13988003840
There is no free space entry for 15305744384-15306821632
There is no free space entry for 15305744384-16135487488
cache appears valid but isnt 15061745664
There is no free space entry for 16377102336-16378097664
There is no free space entry for 16377102336-17209229312
cache appears valid but isnt 16135487488
Wanted bytes 1957888, found 393216 for off 17210597376
Wanted bytes 1072373760, found 393216 for off 17210597376
cache appears valid but isnt 17209229312
There is no free space entry for 22839361536-22840332288
There is no free space entry for 22839361536-23651680256
cache appears valid but isnt 22577938432
There is no free space entry for 27126554624-27128291328
There is no free space entry for 27126554624-27946647552
cache appears valid but isnt 26872905728
There is no free space entry for 27985326080-27987566592
There is no free space entry for 27985326080-29020389376
cache appears valid but isnt 27946647552
There is no free space entry for 30126866432-30127960064
There is no free space entry for 30126866432-31167873024
cache appears valid but isnt 30094131200
Wanted bytes 2195456, found 12288 for off 64471998464
Wanted bytes 1055612928, found 12288 for off 64471998464
cache appears valid but isnt 64453869568
There is no free space entry for 65631424512-65632366592
There is no free space entry for 65631424512-66601353216
cache appears valid but isnt 65527611392
free space inode generation (0) did not match free space cache generation 
(135494)
found 15376998613 bytes used err is -22
total csum bytes: 44021104
total tree bytes: 601505792
total fs tree bytes: 419954688
total extent tree bytes: 10888
btree space waste bytes: 129058353
file data blocks allocated: 126222901248
 referenced 43301400576
Btrfs v3.12

I'm not sure if the corruption is the cause or the consequence of the
kernel panics, which require a hard reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-29 Thread Lenz Grimmer
Hi Joseph, thanks for your quick reply. The problems began some time
after I started using LXC with Btrfs on Trusty, but I'm not sure if a
particular kernel update introduced a regression. I've been using Btrfs
on my home directory previously as well, but did not experience similar
I/O-related crashes.

I'll try using the latest upstream kernel and report back. The problem
is that these crashes happen randomly, I have not yet been able to
reproduce them reliably (and since this always brings down my entire
work environment, I'm not too excited about these crashes, as you can
probably imagine).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415510] Re: Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-28 Thread Lenz Grimmer
Attaching a second screen shot with a slightly different stack trace

** Attachment added: "IMG_20150126_095337.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+attachment/4307319/+files/IMG_20150126_095337.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1415510] [NEW] Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

2015-01-28 Thread Lenz Grimmer
Public bug reported:

I initially reported this as a bug in LXC
(https://github.com/lxc/lxc/issues/424), but I was (rightfully) advised
to report this as a kernel issue instead:

I'm running Ubuntu 14.04.1 LTS (x86_64) on my Laptop. Current Kernel
version is "3.13.0-44-generic". The LXC version is "1.0.7-0ubuntu0.1",
installed from the "ubuntu-lxc" PPA on Launchpad.

I have a dedicated Btrfs file system mounted on /container/, which I use
for storing all LXC containers.

The file system is created on top of a logical volume:

lenz@lenz-ThinkPad-T440 ~ % mount | grep container
/dev/mapper/ubuntu--vg-container on /container type btrfs (rw)
lenz@lenz-ThinkPad-T440 ~ % sudo lvdisplay /dev/mapper/ubuntu--vg-container
  --- Logical volume ---
  LV Path/dev/ubuntu-vg/container
  LV Namecontainer
  VG Nameubuntu-vg
  LV UUIDJUq21P-SSoS-UeU5-rdDS-k6V4-d30e-gJM1FA
  LV Write Accessread/write
  LV Creation host, time lenz-ThinkPad-T440, 2014-09-15 13:42:27 +0200
  LV Status  available
  # open 1
  LV Size65,00 GiB
  Current LE 16640
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   252:5

The hard disk drive is a Samsung SSD ("Samsung SSD 840 EVO 500GB,
EXT0BB0Q, max UDMA/133", according to dmesg).

I have a number containers based on CentOS 6, these were created by
cloning a base image using lxc-clone -s.

Quite frequently, when I create heavy disk I/O in one or several of
these containers (e.g. by running yum update concurrently, or by
transferring large files e.g. via a HTTP upload to one of the container
instances), my host system freezes. This only happens when container
activity is involved, the system runs stable otherwise. Most of the time
the X desktop freezes, sometimes a Kernel panic can be observed on the
console. Unfortunately I'm unable to capture it other than by taking a
picture. The only solution is to perform a cold reboot using the power
button.

This occurred to me before. I then re-created the /container/ file
system from scratch and started again. But now it's happening again, so
I would like to report it for investigation.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.44.51
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lenz   2782 F pulseaudio
 /dev/snd/controlC0:  lenz   2782 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jan 28 16:16:20 2015
HibernationDevice: RESUME=UUID=a60307c3-e53f-473e-ba9e-90cbfe484bb8
InstallationDate: Installed on 2014-09-15 (135 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 20B6005YGE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro softlockup_panic=1 elevator=noop quiet 
splash nomdmonddf nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-44-generic N/A
 linux-backports-modules-3.13.0-44-generic  N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET79WW (2.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B6005YGE
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B6005YGE:pvrThinkPadT440:rvnLENOVO:rn20B6005YGE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20B6005YGE
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug third-party-packages trusty

** Attachment added: "Screen shot of a kernel panic"
   
https://bugs.launchpad.net/bugs/1415510/+attachment/4307289/+files/IMG_20150128_133720.jpg

** Summary changed:

- Frequent kernel panics when doing heavy I/O in containers on Btrfs
+ Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415510

Title:
  Frequent kernel panics when doing heavy I/O in LXC containers on Btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415510/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 571910] Re: Missing Multimedia Plugin "GStreamer element ffdeinterlace"

2014-11-09 Thread Lenz Grimmer
Another "me too" - this problem still exists in 14.04 LTS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571910

Title:
  Missing Multimedia Plugin "GStreamer element ffdeinterlace"

To manage notifications about this bug go to:
https://bugs.launchpad.net/arista/+bug/571910/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1086313] Re: mvlvmbackup lacks support for 'thin' snapshots

2013-06-23 Thread Lenz Grimmer
** Changed in: mylvmbackup
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086313

Title:
  mvlvmbackup lacks support for 'thin' snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/mylvmbackup/+bug/1086313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1086313] Re: mvlvmbackup lacks support for 'thin' snapshots

2012-12-16 Thread Lenz Grimmer
Thanks for the patch, now committed to the trunk.

** Changed in: mylvmbackup
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086313

Title:
  mvlvmbackup lacks support for 'thin' snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/mylvmbackup/+bug/1086313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs