Hi Robert,
Per your pervious discussions with Colin, I'm going to go ahead and mark
this as "Won't Fix" for Hardy. However, the latest Intrepid Ibex 8.10
Alpha release (Alpha 3 at the time of the posting) is available for
testing - http://www.ubuntu.com/testing . If you are able to test and
veri
** Changed in: linux (Ubuntu Hardy)
Status: In Progress => Won't Fix
--
hfsplus oops, corrupted file system
https://bugs.launchpad.net/bugs/202595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Hi Robert,
as for the 64-bit issues, it's always a possibility, and it's hard to
rule that out in this kind of investigation. I'm not sure how much the
hfsprogs and kernel driver's are related, but I imagine stuff to do with
fsck'ing the disk and the kernel driver must be fairly well in-step.
It's
Hello Colin,
> I expect at this point we shall mark this as "Won't Fix" for
> Hardy (since we are so close to the final release) but keep it open
> for
> Hardy + 1.
no problem at all if you do that. Thanks for all your work. I realize
this kind of thing is difficult to track down.
I'm sorry
Hi Robert,
This is going to be a tough bug to debug, as it occurs with a specific
corner case which seems to have triggered it and these king of bugs are
difficult to reproduce. I've had a go and generating a filesystem that
produces the kind of btrees where a node needs rebalancing and causing
an
I've now run fsck.hfs (an i386 binary):
$ ./fsck.hfsplus -d /dev/sdc1
** /dev/sdc1
** Checking HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
Invalid sibling link
(4, 8646)
** Rebuilding Catalog B-tree.
hfs_UNswap_BTNode: inv
Hi Rob,
I would recommend fsck'ing the hfsplus filesystem before you mount it
again just to see if this fixes the broken filesystem, especially
because the filesystem is reporting "hfs: walked past end of dir" - this
alludes to the fact that the underlying btree is messed up somewhere and
needs fi
> sudo dd if=/dev/sdX of=/dev/null
That works without error. Slightly under 20MB/s in case that's of
interest.
Interestingly, Linux mounts the device (complaining it wasn't cleanly
unmounted.) That might have been the case all along -- I'm not sure I
tried accessing it from Linux after the
Hi Rob,
A couple of things. I'd probably make sure that the disk is fully
readable first to see if there are any physical errors on it. A quick
one-liner is the following:
sudo dd if=/dev/sdX of=/dev/null
where /dev/sdX is the name of the device. This basically reads all the
raw blocks from the
Hello,
thanks for looking into this.
On Apr 7, 2008, at 13:40, Colin King wrote:
> 1. Did the running of rdiff-backup trigger the reported Oops and
> cause the broken filesystem?
> 2. Or was the oops caused later when you tried to do rdiff-backup
> on an already broken filesytem?
The oops wa
Hi there,
your report was "Filesystem on a USB disk, journaling disabled, mounted
read-write. rdiff-backup was trying to clean up after a previously aborted
backup. The file system is now broken, Mac OS' Disk Utility failed to repair
the file system. It reported an "invalid sibling link", then
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Colin King
(colin-king)
Status: Triaged => In Progress
--
hfsplus oops, corrupted file system
https://bugs.launchpad.net/bugs/202595
You received this bug notification because you are a member of Ubunt
attaching relevant kern.log
** Attachment added: "kern.log.0"
http://launchpadlibrarian.net/12944209/kern.log.0
--
hfsplus oops, corrupted file system
https://bugs.launchpad.net/bugs/202595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
requested attachments (let's see if this works via mail)
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/12944124/dmesg.log
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/12944125/lspci-vvnn.log
** Attachment added: "uname-a.log"
http://launchpadlibr
Hi there,
Per the kernel team's bug policy, can you please attach the following
information. Please be sure to attach each file as a separate
attachment.
* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
For more informat
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New => Triaged
--
hfsplus oops, corrupted file system
https://bugs.launchpad.net/bugs/202595
You received this bug notification because you are a me
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/12687853/Dependencies.txt
--
hfsplus oops, corrupted file system
https://bugs.launchpad.net/bugs/202595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
17 matches
Mail list logo
