Comment 177 for bug 317781
Revision history for this message
| Graziano (graziano-giuliani-gmail) wrote | #177 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Well, al least it seems that tweaking kernel to allow ext4 to be nice, something has been broken on JFS side....
My box uses JFS for root FS, and all worked OK at least up to two days ago (2.6.28-9, IIRC).
With both 2.6.28-10 and 2.6.28-11, all sort of filesystem corruptions started to pop up, forcing me to a clean reinstall of jaunty (I was upgrading since hardy). And Yes, smartctl says no error on disk AND formatting with badblocks check drags up nothing.
No problem as I have full backups, but it is annoying that top make something new to work developers just break something (yes, old) which was correctly working for years.
As all is lost, only my memory can be of use, and messages were something like:
d_ino != inode number
and file gets (at least with jfs with full name!) wiped. AND we are not speaking about Gnome configuration files, but a whole system update gone with the wind. And when apt and dpkg stop working.....
Geeez....
Graziano