Results 1 to 10 of 13
Thread: iTunes and ext3 :/
Enjoy an ad free experience by logging in. Not a member yet? Register.
iTunes and ext3 :/
Now, for whatever reason, iTunes continually breaks certain sections of the filesystem and every so often I need to run fsck on it in order to get Linux to boot (Fedora 10).
A bit annoying, but meh. The problem is that now, fsck can't actually fix the filesystem, and I can't tell why. So does anyone know of an alternative that I could try?
I'll post the output from my attempts to fix the filesystem in single user mode when I get home, but I know that it always comes up with two unfixed problems, one of which is multiple files of the same name in the same folder. I've seen that problem and fixed it before, but this time fsck won't do it automatically, for some reason. Marks the section to be rebuilt and then does nothing with it.
Is it a Data Partition or / partition of Linux distro?
I would suggest you to use NTFS partition instead of ext3. Linux support NTFS partition very well.
Anyways, boot up in Single User or Rescue Mode and run fsck again. It should fix problems.
It's a shared data partition - mounted on /home
I'd heard that Linux couldn't write to NTFS that well? I'll try that if all else fails though...
No, I've already tried fsck in single user, it doesn't work :/
Not a clue why though, I even ran it once, rebooted back into single user and ran it again - still nothing
Could you post exact error message here? Does system boot up now?
Have you tried to run fsck using LiveCD or mount it in LiveCD?
NTFS is very well supported by Linux and new versions of most of Linux distro including Fedora support NTFS read/write out of box. Fedora 10 support it too.
It won't boot now, no. It forces a filesystem check, which it fails.
I'll post the message when I get home, I don't think it says anything unless you boot into single user though...
No, I've not tried a livecd yet, I'll do that when I get home as well.
And, if all else fails, at least I have a fallback filesystem now - even if it is a proprietry one
Thanks for your help so far
Okay, I've fixed one of the problems, was just a rogue folder. The second is still there though :/
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
Docs contains a filesystem with errors, check forced.
Pass 1: Checking inodes, blocks and sizes
Pass 2: Checking directory structure
Duplicate entry 'Enso?Dot.ipa' found.
Marking /My Music/iTunes/Mobile Applications (7962649) to be rebuilt.
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Docs: ***** FILE SYSTEM WAS MODIFIED *****
Docs: x/y files (4.9% non-contiguous), a/b blocks
It is my impression that writing across filesystems modifies the directory tree. The same happens when you write to Windows from Linux. Upon boot the OS "sees" the checksum is different from when it last came up and tries to correct the error.
In my experience, more than once my writing across has crashed the OS. There must be a threshold, as small writing operations do not cause this behavior. Massive deletes are definitely dangerous.
These are empirical observations which have changed how I write across filesystems. I do not know the technical reasons or ways to modify OS behavior.
As an alternative, you could create a FAT32 partition to keep the data, mountable from both Linux and Windows, and avoid the problem altogether.
02-28-2010 #8Originally Posted by previso
You can find a lot more details at ntfs-3g home page.