From: Gene Heskett <gene.heskett@verizon.net>
To: "Patrick Beard" <patrick@scotcomms.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 VFAT problem
Date: Fri, 14 Nov 2003 09:45:36 -0500 [thread overview]
Message-ID: <200311140945.36537.gene.heskett@verizon.net> (raw)
In-Reply-To: <bp2mab$sts$1@sea.gmane.org>
On Friday 14 November 2003 08:46, Patrick Beard wrote:
>>> FAT: Bogus number of reserved sectors
>>> VFS: Can't find a valid FAT filesystem on dev sda
I'm not getting these messages, but I did just now run
into a weird vfat over usb_storage problem.
Camera is an Olympus C-3020, kernel is 2.6.0-test9-mm3,
the usual configs to allow access to this camera.
The card was about full, so I turned it on and mounted it
as usual. Acessing it with filerunner, I started at the
top of the list, deleting pix I had already downloaded to
/usr/pix. I deleted about 15 in the first batch, then
around 10 in the next batch, and about 20 in the third batch.
Hi-lighting about another 20 and hitting delete got me a
read-only file system error on the last one, but it did
delete the rest of them. I had about 60 left to delete,
but had to umount the camera and turn it off, turn it back
on about 10 secs later, and remount the camera (same device
BTW, thanks guys) about 5 or 6 times before I was able to
get that 64meg card all cleaned out.
And once again, I have NDI if its buggy software in the
camera, or a usb_storage problem.
Here is one such section of the messages log:
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: Write Protect is off
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:19:52 coyote kernel: Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
Nov 14 09:19:52 coyote kernel: Attached scsi generic sg2 at scsi4, channel 0, id 0, lun 0, type 0
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
The "assigned address" was being incremented per disconnect.
And, /dev/camera is a link to /dev/sda1. Is this wrong?
However attempting to mount it useing /dev/sg2 fails, not
a valid block device.
Comments? Screwed up kernel .config? Is mount "-t vfat" the
correct filesystem?
Thanks.
--
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-14 14:45 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 [this message]
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
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=200311140945.36537.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--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®