When I installed Kubuntu 7.04 on my new system (long story short, nothing later will work on my hardware), I used a 3-partition setup: one for system, one for root, and the other devoted entirely to /home. I also chose to format them with the Ext3 filesystem.
Note that this install coexists with a Windows XP Pro install. I cannot use Kubuntu currently because something in xorg.conf is broken, but that's another story.
Should I have formatted my Linux volumes as Ext2 instead? From what I've read, Ext3 is a journaling filesystem, and I'm not sure this is a good thing. It seems to be causing problems with the Windows XP IFS Ext2 driver (homepage here: http://www.fs-driver.org/index.html). Having read the FAQ and troubleshooting sections, I suspect my last shutdown under Kubuntu was not clean, so the volumes were not unmounted properly. According to the FAQ, the Ext2 IFS driver normally works with Ext3 also, but will not open Ext3 volumes if they were not unmounted cleanly. It has something to do with information being present in the "journal" and the driver refusing to mess with it because doing so could potentially result in data loss.
Anyone else used the IFS Ext2 driver under Windows XP? It was working great on another machine, but now that one's having the same problem (can't access Linux volumes from within Windows).
Note that this install coexists with a Windows XP Pro install. I cannot use Kubuntu currently because something in xorg.conf is broken, but that's another story.
Should I have formatted my Linux volumes as Ext2 instead? From what I've read, Ext3 is a journaling filesystem, and I'm not sure this is a good thing. It seems to be causing problems with the Windows XP IFS Ext2 driver (homepage here: http://www.fs-driver.org/index.html). Having read the FAQ and troubleshooting sections, I suspect my last shutdown under Kubuntu was not clean, so the volumes were not unmounted properly. According to the FAQ, the Ext2 IFS driver normally works with Ext3 also, but will not open Ext3 volumes if they were not unmounted cleanly. It has something to do with information being present in the "journal" and the driver refusing to mess with it because doing so could potentially result in data loss.
Anyone else used the IFS Ext2 driver under Windows XP? It was working great on another machine, but now that one's having the same problem (can't access Linux volumes from within Windows).
Comment