Re: gtkpod and Filesystem

2005-12-16 Thread Gunter Ohrner
Alejandro Bonilla wrote:
> 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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: gtkpod and Filesystem

2005-12-16 Thread Gunter Ohrner
Am Freitag, 16. Dezember 2005 18:19 schrieben Sie:
> |>Actually. Issue fixed. It is really odd that a dosfsck fixed it.

I'm glad it helped. :-)

> |i dont see how that is odd.. if the filesystem was somehow corrupted
> |dosfsck would have corrected it.
> Odd how it got "corrupted" and odd on why it would work on Windows and
> not in Linux.

Mh, that's just the same phenomenon one always sees with web sites. If 
some data structure, be it a file system or an HTML-like tag soup, 
doesn't conform to the specification, the processors (fs driber or web 
browser) behavoiur will be implementation dependant... One specific error 
will break one implementation but not the other, while another error will 
just cause the opposite, there may be implementations which are more 
sensitive to specification violation and so on...

So the behaviour you observed is not that surprising, after all. ;)

> Anyway, it works now. I was more worried on the FS Panic than anything
> else.

Well, as I understood it this message just stated that the fs driver was 
confused and blocked write access for safety reasons, to avoid further 
damage.

It had nothing to do with a "kernel panic" or similar.

Greetings and happy music listening,

  Gunter


pgplsOFWjoFNb.pgp
Description: PGP signature


Re: gtkpod and Filesystem

2005-12-16 Thread Gunter Ohrner
Jan Engelhardt wrote:
>>> 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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: gtkpod and Filesystem

2005-12-16 Thread Gunter Ohrner
Jan Engelhardt wrote:
>>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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]