Skip to contentSkip to conversation

gtkpod and Filesystem

DISCUSSION Alejandro Bonilla 3 participants 6 messages Dec 16, 2005 – Dec 17, 2005

lore
Share & tools
lore
#0 lore raw

Hi,

I have Debian Sid with 2.6.15-rc5, I wonder if this could be either with a bug in gtkpod or the kernel (FS Panic).

Whenever I try to sync my Ipod it comes up and says the FS is Write-Procteted or Read-Only. (This is on the gtkpod interface)
"Error opening '/media/IPOD/iPod_Control/Music/F15/gtkpod108107.mp3' for writing (Read-only file system)."

drivers/usb/core/inode.c: creating file '003' Initializing USB Mass Storage driver... usb-storage 1-4:1.0: usb_probe_interface usb-storage 1-4:1.0: usb_probe_interface - got id scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Vendor: Apple Model: iPod Rev: 1.62
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 3999743 512-byte hdwr sectors (2048 MB)
sdb: Write Protect is off
sdb: Mode Sense: 68 00 00 08
sdb: assuming drive cache: write through
SCSI device sdb: 3999743 512-byte hdwr sectors (2048 MB)
sdb: Write Protect is off
sdb: Mode Sense: 68 00 00 08
sdb: assuming drive cache: write through
sdb: sdb1 sdb2
sd 1:0:0:0: Attached scsi removable disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
FAT: Filesystem panic (dev sdb2)
fat_get_cluster: invalid cluster chain (i_pos 120196) File system has been set read-only
FAT: Filesystem panic (dev sdb2)
fat_get_cluster: invalid cluster chain (i_pos 120196)
FAT: Filesystem panic (dev sdb2)
fat_get_cluster: invalid cluster chain (i_pos 120196)
FAT: Filesystem panic (dev sdb2)
fat_get_cluster: invalid cluster chain (i_pos 120196)
FAT: Filesystem panic (dev sdb2)
fat_get_cluster: invalid cluster chain (i_pos 120196)

--
Open WebMail Project (http://openwebmail.org)

#1 lore raw
Quoted 2 lines · Alejandro Bonilla

I have Debian Sid with 2.6.15-rc5, I wonder if this could be either with a bug in gtkpod or the kernel (FS Panic).

Maybe an FS error on your iPod? Did you try to reformat or dosfsck it?

Greetings,

Gunter

#2 lore raw
Quoted 4 lines
Quoted 2 lines

I have Debian Sid with 2.6.15-rc5, I wonder if this could be either with a bug in gtkpod or the kernel (FS Panic).

Maybe an FS error on your iPod? Did you try to reformat or dosfsck it?

Even then, the filesystem code should handle corrupt filesystems more gracefully.

Jan Engelhardt

#3 lore raw
Quoted 4 lines · Jan Engelhardt
Quoted 2 lines
Quoted 1 line

a bug in gtkpod or the kernel (FS Panic).

Maybe an FS error on your iPod? Did you try to reformat or dosfsck it?

Even then, the filesystem code should handle corrupt filesystems more gracefully.

Mh, what's "more gracefully" in the light of fs corruption? The driver just blocked write access to avoid further damage caused by writing to an inconsistent file system which sound perfectly reasonable to me. Writing to a corrupted fs could cause anything to it, depending on the corruption, so better act safe than sorry...

Greetings,

Gunter

#4 lore raw
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 1 line

a bug in gtkpod or the kernel (FS Panic).

Maybe an FS error on your iPod? Did you try to reformat or dosfsck it?

Even then, the filesystem code should handle corrupt filesystems more gracefully.

Mh, what's "more gracefully" in the light of fs corruption?

	return -EIO;

through all instances back to userspace and keep returning EIO for all future requests. But let the user still umount the device.

Quoted 5 lines

The driver just
blocked write access to avoid further damage caused by writing to an inconsistent file system which sound perfectly reasonable to me. Writing to a corrupted fs could cause anything to it, depending on the corruption, so better act safe than sorry...

The interesting part comes when the filesystem corrupts itself
(= the code corrupts the on-disk data), and/plus it does not
notice quickly enough.

Jan Engelhardt

#5 lore raw
Quoted 2 lines · Jan Engelhardt
Quoted 1 line

Mh, what's "more gracefully" in the light of fs corruption?

return -EIO;

In this case you wouldn't even be able to read data from the disk which is not affected by the inconsistencies. If the FS driver switches to readonly mode, that's possible at least. Personally I like such a kind of "Best effort" behaviour. Well, but I'm not the vfat32 driver developer, so who am I to argue? :-)

Greetings,

Gunter