ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

Bug #122369 reported by Matt England on 2007-06-26
Affects Status Importance Assigned to Milestone

Bug Description

Please see this thread for details:


I have been unable to get much attention in the above thread, so I'm posting this bug. I think this a critical issue, for it has to do with data availbility and possibly data integrity breachs within Feisty. I also suspect that the Windows-ext2-mount-via-ifs-driver (see details in above thread) may contribute to this, but that's only speculation (based upon the fact that I'm quite surprised that this error was not caught in community Feisty testing, and the only reasonable explanation I have for this is the Windows-ext2 mount stuff, or a poor Ubuntu testing process; I'd more likely guess the former).

Note that the "In what package did you find this bug?" may not be pertinent for this issue, for it seems premature to attempt to isolate this issue to any one package. Further, it may not be the fault of any one package but a combination or some...or something like that.

Additional info:

Note that I experience data-access problems within the file system mounted on Feisty separate from rdiff-backup. eg, when rsync-ing the file system from one machine to another across a network, the operation hangs (don't have more info at this time). I'm not certain if this happened before or after the aforementioned rdiff-backup run.

Also note that I've been running these same processes/operations for years on the exact same hardware prior to the Feisty (7.04) install. I install Feisty, these symptoms arise. I back-rev the install to Dapper (and re-load the data from backup) and I experience no symptoms.

This bug doesn't take long to duplicate in my system. I have not attempted to duplicate on more than one hardware system.

-Matt England

This problem happens only on a Feisty 7.04 Dekstop edition. I've compared with Dapper (which I'm now running) and have had no problems.

Sorry I didn't state the version of Ubuntu more clearly at the top (I originally had it listed in the "package" section, but launchpad wouldn't let me do that, and I forgot to change the bug body appropriately).

I'm not sure if I've mentioned this previously, but past experience has shown that these symptoms are somewhat repeatable/demonstratable on my system.

This is a data-integrity problem--it destorys my data--and is preventing me from upgrading from 6.06.1, which causing all sorts of other problems.

After 2 months I have heard of no one asking me about this problem. Is it that bugs are not sorted by order of importance, that data integrity problems are not necessarily important, or that no one else is complaining about this...or some combination of the above?

I'm rather disappointed that because of this bug, I have no upgrade path. I'm further disappointed that after 2 months, I can't find support for this problem. Even if no one else reports it, would not data-integrity symptoms merit some kind of anlaysis?

To reiterate: I experience none of these problems with the same hardware when running 6.06.1.


I was under the impression that I could not upgrade to 6.10. Rereading my original notes, it looks like I have yet to either try 6.10 or have not see symptoms under 6.10. Upgrading to 6.10 may help me a lot. I'll look into trying that later.

If 6.10 does not experience this problem (and 6.10 presents the upgrade features that I need/want), then this bug becomes less of an issue for me.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers