Hi Stefan, 2016-03-07 20:58 GMT+01:00 Stefan Seyfried <stefan.seyfried@googlemail.com>:
Hi René,
not wrapping the lines would make reading much easier :-)
I'd like to do so, but this mailing lists requires plain text mails and the Google Mail web front-end does automatically wrap lines in plain-text mails during sending (not editing) to be RFC-compliant and I haven't found any setting to deactivate this. Do you have an idea how to avoid this? Did I miss some setting anywhere?
Am 04.03.2016 um 12:28 schrieb René Krell:
One might already have noticed, the backtrace above is already the secondary crash while failing to mount the XFS partition using the Kernel:Stable kernel. The initial crash of the original Tumbleweed kernel was this one: [...] 2016-03-04T09:34:42.592320+01:00 rkrell kernel: [ 3442.618264] 2016-03-04T09:34:42.592320+01:00 rkrell kernel: [ 3442.618265] Leftover inexact backtrace: 2016-03-04T09:34:42.592321+01:00 rkrell kernel: [ 3442.618265] 2016-03-04T09:34:42.592321+01:00 rkrell kernel: [ 3442.618298] XFS (sdb2): xfs_do_force_shutdown(0x8) called from line 991 of file ../fs/xfs/xfs_trans.c. Return address = 0xffffffffa12efdef 2016-03-04T09:34:42.639602+01:00 rkrell kernel: [ 3442.662619] XFS (sdb2): Corruption of in-memory data detected. Shutting down filesystem 2016-03-04T09:34:42.639614+01:00 rkrell kernel: [ 3442.662624] XFS (sdb2): Please umount the filesystem and rectify the problem(s)
2016-03-04T09:34:42.687591+01:00 rkrell kernel: [ 3442.709922] Buffer I/O error on dev sdb2, logical block 137122852, lost async page write
This sounds like a hardware problem (the hardware below your XFS file system). Is it possible that such I/O errors happened before 09:34:42.592256 already?) --
I' can't really find any hint, just: 2016-03-04T08:37:28.638917+01:00 rkrell kernel: [ 4.139335] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 2016-03-04T08:37:28.638917+01:00 rkrell kernel: [ 4.143512] ata2.00: ATA-8: WDC WD7500BPKX-00HPJT0, 01.01A01, max UDMA/133 2016-03-04T08:37:28.638920+01:00 rkrell kernel: [ 4.143515] ata2.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA 2016-03-04T08:37:28.638921+01:00 rkrell kernel: [ 4.148401] ata2.00: configured for UDMA/133 2016-03-04T08:37:28.638921+01:00 rkrell kernel: [ 4.148724] scsi 1:0:0:0: Direct-Access ATA WDC WD7500BPKX-0 1A01 PQ: 0 ANSI: 5 2016-03-04T08:37:28.638922+01:00 rkrell kernel: [ 4.149075] sd 1:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/699 GiB) 2016-03-04T08:37:28.638922+01:00 rkrell kernel: [ 4.149079] sd 1:0:0:0: [sdb] 4096-byte physical blocks 2016-03-04T08:37:28.638923+01:00 rkrell kernel: [ 4.149396] sd 1:0:0:0: [sdb] Write Protect is off 2016-03-04T08:37:28.638924+01:00 rkrell kernel: [ 4.149400] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 2016-03-04T08:37:28.638926+01:00 rkrell kernel: [ 4.149463] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 2016-03-04T08:37:28.638927+01:00 rkrell kernel: [ 4.164820] sdb: sdb1 sdb2 2016-03-04T08:37:28.638927+01:00 rkrell kernel: [ 4.165586] sd 1:0:0:0: [sdb] Attached SCSI disk I can send you the whole log to your private mail, if this would help. I cannot exclude a hardware problem, but it has been the only "user-visible" problem to this time with this disk. I use it already several months. Another fact is there was a bunch of XFS changes during the transition from 4.4.2 to 4.4.3, just have a look to https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.3. Isn't it possible there has been introduced some race or something similar? The crash occurred while doing extensive disk operations (Maven compilation, launching a Java IDE and similar etc. at the same time). 2016-03-07 20:58 GMT+01:00 Stefan Seyfried <stefan.seyfried@googlemail.com>:
Hi René,
not wrapping the lines would make reading much easier :-)
Am 04.03.2016 um 12:28 schrieb René Krell:
One might already have noticed, the backtrace above is already the secondary crash while failing to mount the XFS partition using the Kernel:Stable kernel. The initial crash of the original Tumbleweed kernel was this one: [...] 2016-03-04T09:34:42.592320+01:00 rkrell kernel: [ 3442.618264] 2016-03-04T09:34:42.592320+01:00 rkrell kernel: [ 3442.618265] Leftover inexact backtrace: 2016-03-04T09:34:42.592321+01:00 rkrell kernel: [ 3442.618265] 2016-03-04T09:34:42.592321+01:00 rkrell kernel: [ 3442.618298] XFS (sdb2): xfs_do_force_shutdown(0x8) called from line 991 of file ../fs/xfs/xfs_trans.c. Return address = 0xffffffffa12efdef 2016-03-04T09:34:42.639602+01:00 rkrell kernel: [ 3442.662619] XFS (sdb2): Corruption of in-memory data detected. Shutting down filesystem 2016-03-04T09:34:42.639614+01:00 rkrell kernel: [ 3442.662624] XFS (sdb2): Please umount the filesystem and rectify the problem(s)
2016-03-04T09:34:42.687591+01:00 rkrell kernel: [ 3442.709922] Buffer I/O error on dev sdb2, logical block 137122852, lost async page write
This sounds like a hardware problem (the hardware below your XFS file system). Is it possible that such I/O errors happened before 09:34:42.592256 already?) -- Stefan Seyfried
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
"Your mail is 7 pages of printout. Do you seriously expect people that do openSUSE in their free time to read that? Little less Castro, little more JFK..." -- coolo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org