[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT ent
From: |
felix |
Subject: |
[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT entries |
Date: |
Mon, 25 Jul 2016 12:42:20 -0000 |
** Patch added: "Patch to fix the qemu-img issue (does NOT resolve the whole
bug)"
https://bugs.launchpad.net/qemu/+bug/1599539/+attachment/4707063/+files/make_vvfat_work_with_qemu-img.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1599539
Title:
2.6.0: vvfat driver generates bad FAT entries
Status in QEMU:
New
Bug description:
The vvfat driver sometimes generates entries about which file system
checking utilities generate complaints.
For example, dosfsck will complain that the volume label entry has
non-zero size. ScanDisk from Windows 9x complains about invalid dot
(".") and dot-dot ("..") entries in directories and also about invalid
long file name entries. MS-DOS ScanDisk also often manages to find
"lost clusters" on the drive.
Tangentially: qemu-img convert fat:test test.img doesn't seem to work
-- it generates an 504MiB of zero bytes and hangs. qemu-img map
fat:test generates an assertion failure. Having qemu-img working might
have helped with debugging the above issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1599539/+subscriptions