Comment 20 for bug 125702
Revision history for this message
| mikeXYZ (qmikeq) wrote Re: failure to umount local filesystems - gutsy tribe 2 | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
For me, same as reported by waxhell (above). Issue with: Kubuntu 7.10 on UFD, Live Persistent.
I've tried using ext3 and I get the same segmentation fault. I did not test the extent of data corruption using ext3 (vs ext2), but I suspect it will show up upon repeated re-boots.
I have also seen the issue regarding “trying to unmount the /cow directory.”
The extent of data corruption gets worse upon the second re-boot (X messes up so badly that the issue is moot on the third re-boot).
I have no problems with the straight Live Kubuntu on UFD (without persistence). Ron Z's comments on that are noted.
Specifically, as said by waxhell (2007-10-29):
“I may have this bug in Gutsy release, however in my instance, I get a seg fault. Persistence enabled on a pen-drive. Experiencing some data corruption as a result of this (not all files are copied properly to the casper-rw partition) Reference Bug #147117
Umounting local filesystem [fail]
umount2: Device or resource busy
umount: /cdrom busy - remounted read only
Segmentation fault [fail]