[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049267

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-25 Thread xor
I was going to install the latest mainline kernel. HOWEVER - dpkg-sig --list shows that the packages contain no signatures at all. - Further, there doesn't seem to be any signature files on the webserver [0] - The webserver does not accept https connections. While installing a release-candidate

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-24 Thread xor
I now did the following: - I put the disks of an affected machine (not the original one in this bug report) into a Debian6 machine which has been running rock-solid with XFS for years - I used a script of my own to generate checksums file date listing of ALL files (~2.5TB) on the disks using

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-17 Thread Joseph Salisbury
As requested in comment #4, it would be helpful to know if this bug also exists upstream, as well as bug 1051689 . There is no indication that this specific issue is already fixed upstream, but testing the mainline kernel will prove or dis-prove that. -- You received this bug notification

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-16 Thread xor
apport information ** Tags added: apport-collected staging ** Description changed: Using Ubuntu 12.04 server, we installed a machine using the following disk layout: XFS = dm-crypt = RAID5. A *complete* list of ALL configuration of the machine including the setup can be provided if

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-16 Thread xor
NOTICE: This happened on the same machine as bug #1051689. After the machine suffered from #1051689, we tried to do a full-backup of the machine on ext4, which then also crashed due to a NULL pointer dereference. Maybe the underlying issue is a RAID/dm-crypt bug? Both the XFS and ext4 were on

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-14 Thread xor
(In reply to bot comment #3: We will try to do that. We hope that apport-collect is not a GUI application since the affected machine does not have an X-Server) In reply to comment #4: Do you have an actual indication that the upstream kernel would fix this? In other words: Does its changelog

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-12 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. Once you've tested the

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-11 Thread xor
After that, what happened very often is the following: Sep 10 11:58:11 server kernel: [386031.913144] BUG: soft lockup - CPU#0 stuck for 23s! [kswapd0:35] Sep 10 11:58:11 server kernel: [386031.913200] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage uas nfsd nfs lockd fscache

[Bug 1049267] Re: XFS corruption on machine which never suffered a hard reset or disk failure

2012-09-11 Thread Edward Donovan
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049267 Title: XFS corruption on machine which never suffered a hard reset or disk failure To manage