All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Shubham Kumar <kumar.shubham@research.iiit.ac.in>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] regarding bug name : -hda FAT:. limited to 504MBytes
Date: Wed, 15 Feb 2017 11:10:52 +0100	[thread overview]
Message-ID: <20170215101052.GA4935@noname.redhat.com> (raw)
In-Reply-To: <6066bf52-d3d9-07d2-1e0f-118b8c19f3f4@redhat.com>

Am 14.02.2017 um 23:24 hat Thomas Huth geschrieben:
> On 14.02.2017 22:38, Shubham Kumar wrote:
> > Since the problem seems like the used FAT-16 file system , 
> > Will it solve the problem if I change the code of  vvfat.c for FAT-32 file system to increase acceptable file size ?
> 
> As far as I know, FAT16 can already support up to 4GB file systems, so
> that limitation to 504 MB must be something different.
> It's maybe best if you put the qemu-block mailing list on CC:, to get
> the attention of the block/disk expert, too. Maybe there's someone
> around who knows the vvfat code and its limitations and can give a good
> answer here...

None of the active developers know, or want to know, the vvfat code.

There is some FAT32 support there, but if you use it:

    fprintf(stderr, "Big fat greek warning: FAT32 has not been tested. "
                    "You are welcome to do so!\n");

So if you just want to play with it, go ahead. But if you care about
your data, maybe vvfat isn't the right tool anyway.

Kevin

      reply	other threads:[~2017-02-15 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 21:38 [Qemu-devel] regarding bug name : -hda FAT:. limited to 504MBytes Shubham Kumar
2017-02-14 22:24 ` Thomas Huth
2017-02-15 10:10   ` Kevin Wolf [this message]

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=20170215101052.GA4935@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=kumar.shubham@research.iiit.ac.in \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.