Today, our IMAP server has been struck by this bug.
We're still running hardy and i'm aware that it is not supported since
May 2013 but it's sad that this problem was not addressed before hardy
EOL. Maybe it wasn't an easy task to backport the Jan 2009 fix mentioned
in #7 to hardy kernel, too bad
Leann,
please look at the report. Comment #7 written on 2009-06-03 clearly
indentifies the problem and has a link explaining details.
This bug is not reproducable. I got it on a high-usage-server after more
than one year of usage and on a another box which isn't used heavily
after few month.
Thanks for the update Brian. I'll just go ahead and close this out per
your previous comment.
** Changed in: linux (Ubuntu)
Status: Incomplete = Won't Fix
--
XFS internal error xfs_trans_cancel at line 1164 of file
/build/buildd/linux-2.6.27/fs/xfs/xfs_trans.c
Hi Brian,
Please be sure to confirm this issue exists with the latest development
release of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/releases/karmic . If the issue remains,
please run the following command from a Terminal
(Applications-Accessories-Terminal). It will
On Wed, 2009-09-02 at 00:22 +, kernel-janitor wrote:
Hi Brian,
Hi.
Please be sure to confirm this issue exists with the latest development
release of Ubuntu.
No thanks. I will not risk another byte of data or any more of my time
to XFS thank you very much.
ISO CD images are available
This bug is known and already solved - but not for Ubuntu:
On the kernel side the big excitement in January was an in-memory corruption
introduced in the btree refactoring which hit people
running 32bit platforms without support for large block devices. This issue
was fixed and pushed to
Final follow-up;
On Februari 9th, the filesystem became unmountable and unrepairable.
We copied the logical volume to an external harddisk for analysis by
Kroll Ontrack. It took their engineers 4 weeks to finalize this; they
told me that they had never experienced this much corruption before but
On Mon, 2009-03-23 at 08:19 +, Ronald van Engelen wrote:
In spite of Brian's remarks I really think it was caused by the unique
hardware-failure inside the server (somehow it killed power to all
internal components). In my opinion, XFS is still rock solid (as long as
there's some juice)
The two instances of this that I have experienced did not involve any
hardware failures of any sort.
The first instance was relatively painless as the filesystem was
relatively empty.
The second instance however took almost 24h to xfs_repair and I only did
the repair so that I could get the data
Some updates which might explain the failure I've seen.
During december (about a month after my post) our server shut itself
down two times at night. Furthermore, nfs-kernel-server disappeared each
day. While we were analyzing this, the server finally shutdown again one
night in january and
Damnit. Just got another one of these. Is nobody from Ubuntu going to
even triage this report? This is a very serious bug for anyone using
the XFS filesystem.
Jan 26 12:59:32 pc kernel: [678572.673862] Pid: 32373, comm: rsync Tainted: P
2.6.27-10-generic #1
Jan 26 12:59:32 pc kernel:
Same error occured here; without any hints (not out of ram no other
errors) the filesystem was shutdown.
System details:
* hardy 2.6.24-16-server x86_64 (2.6.24-16.30), xfsprogs 2.9.4-2, lvm2
2.02.26-1ubuntu9
* dual 3ware 9660 SAS-controllers in raid 6, coupled together in dm raid0
After the
12 matches
Mail list logo
