public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ali Akcaagac <aliakc@web.de>
To: linux-kernel@vger.kernel.org, aebr@win.tue.nl
Subject: Re: [BUG] FAT broken in 2.6.7-bk15
Date: Sun, 04 Jul 2004 14:34:55 +0000	[thread overview]
Message-ID: <1088951695.596.7.camel@localhost> (raw)

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

> > The recent changes in 2.6.7-bk15 broke FAT support. I am doing some
> > rescue backup systems here using tools like syslinux and mtools to
> > format a normal msdos disk (for el-torito). I figured out that after
> > creating and formating of these disks that it is impossible to mount
> > them with 'msdos' or 'vfat'.

> You may be able to check for yourself precisely which change caused
> trouble for you. The only very recent change is one that makes the
> kernel more permissive.

> Give details on what versions work for you, what versions don't.
> Give the exact error messages. Give the first few sectors of the
> filesystem that you cannot mount but can mount with an earlier kernel.

Ok after some further research I figured this out. My last working
version of the Linux Kernel was 2.6.7 which worked with my rescue
system. I now applied the bk* patches upwards to check which one caused
the issue and I figured that this happened between bk3 to bk4 (so the
problem occoured with the bk4 patch). The diskimage was created with
mtools 3.9.9 and worked perfectly before.

export MTOOLSRC=".mtools.conf"
echo "drive a: file=\"/tmp/bootflop.img\" mformat_only" > .mtools.conf
dd if=/dev/zero of=/tmp/bootflop.img count=5760 bs=512
mformat -t 80 -h 2 -s 36 A:
rm .mtools.conf

The diskimage was created that way for countless months without any
problems. You find the image as attachment. After bunzip'ing it you
receive a 2,88 mb file (don't worry about the tiny size now) with the
md5sum: dc27cfe332cf96238e80d148c9955b9e

[-- Attachment #2: bootflop.img.bz2 --]
[-- Type: application/x-bzip, Size: 231 bytes --]

             reply	other threads:[~2004-07-04 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-04 14:34 Ali Akcaagac [this message]
2004-07-04 16:36 ` [BUG] FAT broken in 2.6.7-bk15 OGAWA Hirofumi
  -- strict thread matches above, loose matches on Subject: below --
2004-07-05  6:08 Ali Akcaagac
2004-07-05  4:50 Ali Akcaagac
2004-07-04 22:11 Ali Akcaagac
2004-07-04 22:17 ` Jesse Stockall
2004-07-05  5:02 ` OGAWA Hirofumi
2004-07-04 11:28 Ali Akcaagac
2004-07-04 12:18 ` Andries Brouwer
2004-07-04 13:44 ` Jesse Stockall

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=1088951695.596.7.camel@localhost \
    --to=aliakc@web.de \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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