Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: linux-ec2 (Ubuntu Hardy)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package linux-ec2 - 2.6.32-316.31
---
linux-ec2 (2.6.32-316.31) lucid-proposed; urgency=low
[ Stefan Bader ]
* XEN: x86: Flush TLB if PGD entry is changed in i386 PAE mode
- LP: #742056
* XEN: x86: Emit mem=nopentium ignored warning when not
This bug was fixed in the package linux-ec2 - 2.6.31-308.29
---
linux-ec2 (2.6.31-308.29) karmic-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #737761
[ Brad Figg ]
* Rebased to 2.6.31-23.75
[ Ubuntu: 2.6.31-23.75 ]
* Release Tracking Bug
-
Can confirm that 2.6.32-316-ec2 fixes my problems with xfsdump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT
This bug was fixed in the package linux - 2.6.31-23.75
---
linux (2.6.31-23.75) karmic-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #737663
[ Upstream Kernel Changes ]
* do_exit(): make sure that we run with get_fs() == USER_DS,
CVE-2010-4258
On our server we tested this fix on, I disconnected the testing
repository. This morning I was notified that linux-image-2.6.32-31
-generic-pae_2.6.32-31.61_i386.deb was available. I pulled down that
build, IPL'ed, and performed a backup. The backup completed flawlessly.
Next up, testing this same
This bug was fixed in the package linux - 2.6.32-31.61
---
linux (2.6.32-31.61) lucid-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #754842
[ Upstream Kernel Changes ]
* x86, quirk: Fix SB600 revision check
- LP: #742056
linux (2.6.32-31.60)
Checking in on this... Is there additional testing which needs to get
done? Or is this code ready to release to Lucid stable? Is there an ETA
as to when this update will be distributed to Lucid stable? Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package linux - 2.6.24-29.88
---
linux (2.6.24-29.88) hardy-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #736290
[Steve Conklin]
* Ubuntu-2.6.24-29.87
* [Config] Allow insertchanges to work in later version chroots
I've also been running xfsdump/amanda via proposed kernel for Lucid, and
it works great. Thanks! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and
I have been running xfsdumps on both Karmic and Hardy with the proposed
kernel and both passed.
** Tags added: verification-done-hardy verification-done-karmic
** Tags removed: verification-needed-hardy verification-needed-karmic
--
You received this bug notification because you are a member of
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove
** Branch linked: lp:ubuntu/lucid-proposed/linux-mvl-dove
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression
Today I installed kernel:
linux-image-2.6.32-31-generic-pae_2.6.32-31.60_i386.deb
To hopefully test the fix on Lucid. The backup went through 100%. That
is a good thing.
However I saw a few warnings when it was backing up the /etc directory.
The backup command run was as following, then the full
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed'
to 'verification-done'.
If verification is not done by one week from today, this fix will
** Tags added: verification-needed-karmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT
errno = 22
--
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed'
to 'verification-done'.
If verification is not done by one week from today, this fix will
I've verified that the proposed Linux nitwo-ubuntu 2.6.32-31-generic
#60-Ubuntu SMP Thu Mar 17 22:15:39 UTC 2011 x86_64 GNU/Linux fixes the
problem.
I also confirmed that the warnings noted in #30 appear to be harmless; I
see them too but the resulting dump includes the files and the restored
@Bill Nickless #33, thank you for your quick work in both verifying and
taking a shot at updating the tags on this bug report. Hopefully soon
these new Lucid kernels will be released, and this problem will fade
into memories... :-)
--
You received this bug notification because you are a member
Michael,
we only have a proposed update for Ubuntu 8.04 LTS (hardy) at the
moment. Updates for 10.04 LTS (lucid, which you are using) will follow
shortly and will be announced here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Accepted linux-ec2 into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Also affects: linux-ec2 (Ubuntu)
** Branch linked: lp:ubuntu/karmic-proposed/linux-ec2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT
errno = 22
--
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT
errno = 22
--
Greetings Martin, Thank you for this invitation. This morning I followed
the step in the documentation you posted a link to. I do not see an
updated kernel version queue up for installation. I suppose that is to
be expected as I only have the -26 kernel installed.
Manually looking through (in
Added backports for Lucid, Karmic and Hardy to be included for the next
proposed cycle. It was decided to skip Dapper. First I could not see
that problem there (there were rather other problem which I could not
really claim to be a regression as its not clear how well xfs worked
back then). Also
Thank you so much Stefan!
I switched over 100% to Ubuntu with 7.04 (Feisty Fawn) and XFS has been
very stable since then. (Other than 7.10 which was the worst release
ever, and I never did get a 7.10 box to production state!)
What about maverick (10.10) and also natty? Are these versions also
Maverick and later are ok because the missing patch came in before Maverick. As
soon as kernels with the missing patch are uploaded into proposed there will be
a request for testing posted to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Regression problem is still present in Lucid 2.6.32-29:
d3m406@nitwo-ubuntu:~$ gunzip ~/Desktop/100mb.xfs.gz /tmp/100mb.xfs
d3m406@nitwo-ubuntu:~$ sudo mkdir -p /mnt/100mb
d3m406@nitwo-ubuntu:~$ sudo mount -o loop /tmp/100mb.xfs /mnt/100mb
d3m406@nitwo-ubuntu:~$ sudo xfsdump /mnt/100mb -f
I see this has been reproduced on a small filesystem, but for future reference
xfs
has a utility called xfs_metadump that helps in these situations. It grabs just
the
metadata, so it results in a relatively small file, and the file can then be
exploded back
into a sparse image of the original
For posterity, CVE-2010-2943 (http://cve.mitre.org/cgi-
bin/cvename.cgi?name=CVE-2010-2943) only listed 3 patches despite the
initial patch being a series of 4 commits.
https://bugzilla.redhat.com/show_bug.cgi?id=624923 shows all 4 patches.
(Plus a QA patch and an additional patch to fix a
Maybe I am missing something. In order to check whether older releases
might be affected, I created a xfs fs (mkfs.xfs /dev/...), mounted it
and run xfsdump -p10 -Ltest -Mdump -f outfile mount on it. Still I
am not able to trigger the error (even in Lucid). Is there a quick way
to re-create this
@Stefan #8, On our server which I first saw the crash on, only three out
of the eight or so xfsdump backups regularly scheduled caused this
crash. The others all backed up successfully. The dump I originally
started this case with actually produced a partial backup size. The
other two backup jobs
Right, Dann Frazier has pointed out the missing patch in comment #4 on
this bug. So for 2.6.32 we should have the fix. I am trying to work out
the way to proceed for older releases as the same four patches that have
been identified as causing the regression on Lucid, have been backported
to
Hi Stefan,
Thanks for your work on this one! The one filesystem we use 'xfsdump'
on is our BackupPC pool filesystem which is relatively large and
densely populated with files. Since upgrading the kernel as the others
described xfsdump always fails immediately on that filesystem. It's a
900GB
For what it's worth, I use xfs for the root and /home filesystem on my
Dell M6500. /home is also encrypted with ECRYPTFS. Since -26, xfsdump
always fails immediately on both filesystems. I've been rebooting back
to -26 to perform my weekly backups to offline media.
--
You received this bug
I have a 100mb xfs filesystem that causes xfsdump to fail every time. I
created it by copying /usr/include to a newly created xfs filesystem
within a file in /tmp/, deleting a few files, and then restoring them
from /usr/include again. Should I attach it to this bug, or would you
like me to put
I found that gzip'ing the image makes it small enough to attach to this
bug. So to replicate the problem under -28, download the attached file
and do the following:
d3m406@nitwo-ubuntu:/tmp$ gunzip ~/Desktop/100mb.xfs.gz /tmp/100mb.xfs
d3m406@nitwo-ubuntu:/tmp$ sudo mkdir -p /mnt/100mb
Thanks for all the pointers. So size seems to matter in this case. :) I
copied over more data to the xfs fs and this seems to trigger the bug.
So now I can go back on releases and make sure about the status there.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For Maverick (2.6.35) the prereq patch is already included and the same
for current development (Natty).
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: linux
** Description changed:
+ SRU Justification:
+
+ Impact: The patches backported to fix CVE-2010-2943 caused a regression
+ for xfsdump.
+
+ Fix: Backporting one more patch from upstream is fixing the issue.
+
+ Testcase:
+ 1. create an xfs filesystem with data (~100MB). There is a compressed
Thanks for the Lucid backport Dann. When looking quickly at the CVE, it
seems that beside of Lucid, this would also affect Karmic, Hardy, and
Dapper. I will check and make sure that we update all potentially
affected releases.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
**
According to http://oss.sgi.com/archives/xfs/2011-02/msg00085.html,
Ubuntu also needs the xfs: always use iget in bulkstat fix. fyi, I
included this change in the backport I did to fix CVE-2010-2943 in
2.6.32-longterm/Debian.
I'll attach a copy of this change ported to lucid.
** CVE added:
Thank you so much Dann! Please let me know if you would like me to
install an updated kernel package, and from where, to confirm the fix
for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
I'm also affected by this bug. I'm running the 2.6.32-28 virtual kernel
in a KVM host.
root@db-sec-slave:~# xfsdump -f /var/tmp/xfsdump /vol
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.0.4 (dump format 3.0) - Running single-threaded
= dump
I cross reported this bug to the SGI Linux XFS support group. Bill
Kendall of SGI replied as follows:
===
On 02/02/2011 07:30 AM, Michael Lueck wrote:
Greetings,
Somehow a reported IRIX bug with XFS got into Ubuntu 10.04 (Lucid) starting
with kernel 2.6.32-27.
I am
Problem still exists under 2.6.32-28 on x86_64:
+ sudo xfsdump -p 10 -L NITWO Ubuntu Home Filesystem -M Written 2011-01-26 -f
/media/tvms/Backups/nitwo-ubuntu/home/2011-01-26.xfsdump /home
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.0.4 (dump format 3.0) - Running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692848
Title:
Regression between 2.6.32-27 and 2.6.32-26 xfsdump SGI_FS_BULKSTAT errno = 22
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
46 matches
Mail list logo
