mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vid Strpic <vms@bofhlet.net>
To: Patrick Beard <patrick@scotcomms.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 VFAT problem
Date: Sat, 15 Nov 2003 10:08:01 +0100	[thread overview]
Message-ID: <20031115090801.GV21265@home.bofhlet.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On Fri, Nov 14, 2003 at 01:46:51PM -0000, Patrick Beard wrote:
> >> FAT: Bogus number of reserved sectors
> >> VFS: Can't find a valid FAT filesystem on dev sda
> >Oh, no, not again... :(
> >We had the same problem few weeks ago... a patch is in the archives, it
> >worked for me.
> I did apply Andries's 'Relax FAT checking' patch last night but the only
> difference I noticed was my belkin reader changed it's error to 'no media
> found' the camera still gave 'wrong fs...'

Hmmm.

> After advice from Philippe and Andries and the following I found on a
> website;
> "The problem is that Linux only looks at the disk geometry the first time
> the camera is plugged in. So when you unplug the camera and change the
> memory card Linux does not check to see if the geometry has changed."

I didn't know that... it shouldn't happen?  I don't connect my camera by
usb-storage, I have a card reader, and it really behaves as removable
media device, as it should - checks size everytime.  Maybe we should
change something here?

> I really hope I've not chased my tail by hitting the following combination
> 'up-patched inode.c' + 'trying to use sda after a deja search' and finally
> 'Linux only checking the geometry once'. I'd like to put this thread on hold
> until I take stock of the steps I've taken just to make sure I've not been a
> right 'plum'.

Well, those things sometimes take a lot of time.

-- 
           vms@bofhlet.net, IRC:*@Martin, /bin/zsh. C|N>K
Linux moria 2.6.0-test9 #1 Sat Oct 25 23:00:37 CEST 2003 i686
 10:05:31 up 9 days, 19:22,  1 user,  load average: 0.30, 0.48, 0.29
Eagles may soar, but weasels don't get sucked into jet engines.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-11-15  9:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15  9:08 Vid Strpic [this message]
  -- strict thread matches above, loose matches on Subject: below --
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 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
2003-11-15 18:06   ` Parick 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=20031115090801.GV21265@home.bofhlet.net \
    --to=vms@bofhlet.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®