From: Gene Heskett <gene.heskett@verizon.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: "Patrick Beard" <patrick@scotcomms.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 VFAT problem
Date: Fri, 14 Nov 2003 18:59:59 -0500 [thread overview]
Message-ID: <200311141859.59669.gene.heskett@verizon.net> (raw)
In-Reply-To: <20031114202339.GB18107@win.tue.nl>
On Friday 14 November 2003 15:23, Andries Brouwer wrote:
>On Fri, Nov 14, 2003 at 09:45:36AM -0500, Gene Heskett wrote:
>> Nov 14 09:19:51 coyote kernel: hub 3-2:1.0: new USB device on port
>> 3, assigned address 9 Nov 14 09:19:51 coyote kernel: scsi4 : SCSI
>> emulation for USB Mass Storage devices Nov 14 09:19:52 coyote
>> kernel: Vendor: OLYMPUS Model: C-3020ZOOM(U) Rev: 1.00 Nov
>> 14 09:19:52 coyote kernel: Type: Direct-Access
>> ANSI SCSI revision: 02 Nov 14 09:19:52 coyote kernel: SCSI
>> device sda: 128000 512-byte hdwr sectors (66 MB) Nov 14 09:19:52
>> coyote kernel: sda: assuming drive cache: write through Nov 14
>> 09:19:52 coyote kernel: sda: sda1
>> Nov 14 09:20:34 coyote kernel: FAT: Filesystem panic (dev sda1)
>> Nov 14 09:20:34 coyote kernel: fat_free: deleting beyond EOF
>> (i_pos 0) Nov 14 09:20:34 coyote kernel: File system has been
>> set read-only
>>
>> Comments? Screwed up kernel .config? Is mount "-t vfat" the
>> correct filesystem?
>
>It would have been interesting to see the filesystem after this
> error message. Can you reproduce the error?
>
>(vfat? I don't know - most cameras just use msdos, but vfat doesnt
> harm, I suppose)
>
>The error message means that the fatfs followed a chain of clusters
> in order to delete them all and found a free cluster before finding
> an end-of-file mark.
And I could possibly have created that empty sector by not treating
the card as a LIFO I suppose... Makes a certain amount of sense, but
why did a powerdown and a reconnect fix it? Some compacting routine
in the cameras soft maybe?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2003-11-15 0:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 11:32 Vid Strpic
2003-11-14 13:46 ` Patrick Beard
2003-11-14 14:45 ` Gene Heskett
2003-11-14 17:45 ` OGAWA Hirofumi
2003-11-14 18:51 ` Gene Heskett
2003-11-14 19:13 ` Maciej Zenczykowski
2003-11-14 19:58 ` Gene Heskett
2003-11-14 20:30 ` Maciej Zenczykowski
2003-11-15 0:05 ` Gene Heskett
2003-11-14 20:02 ` OGAWA Hirofumi
2003-11-14 23:56 ` Gene Heskett
2003-11-15 8:41 ` OGAWA Hirofumi
2003-11-15 10:19 ` Gene Heskett
2003-11-15 11:31 ` OGAWA Hirofumi
2003-11-14 20:23 ` Andries Brouwer
2003-11-14 23:59 ` Gene Heskett [this message]
2003-11-15 18:06 ` Parick Beard
-- strict thread matches above, loose matches on Subject: below --
2003-11-15 9:08 Vid Strpic
2003-11-14 11:51 Patrick Beard
2003-11-14 19:03 ` Andries Brouwer
2003-11-14 20:06 ` Gene Heskett
2003-11-14 20:15 ` OGAWA Hirofumi
2003-11-17 9:46 ` Patrick Beard
2003-11-14 9:39 Patrick Beard
2003-11-14 11:38 ` Andries Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200311141859.59669.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@scotcomms.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®