Displaying 8 results from an estimated 8 matches for "sectors_per_cluster".
2015 Nov 09
6
[PATCH 0/5] build: Enable some more warnings.
Add some warnings. Well, the first patch is a miscellaneous
change, but patches 2-5 add some warnings.
Rich.
2016 Feb 26
0
[PATCH 1/5] fat: fix minfatsize for large FAT32
...d
at least test the values that are around or close to the limits between
FAT12/16/32.
For simplicity, I'll give basic examples (which I have not truly
analyzed; developers could / should test relevant code).
Example A:
Volume_Total_Sectors: 66'463
FAT type: FAT32
Bytes_per_sector: 512
Sectors_per_Cluster: 1
Sectors_per_FAT: 511 ---> this value should _not_ be accepted as valid
minfatsize; 512 should be OK.
Example B:
Volume_Total_Sectors: 4'187'104
FAT type: FAT32
Bytes_per_sector: 512
Sectors_per_Cluster: 64
Sectors_per_FAT: 511 ---> this value should _not_ be accepted as valid
mi...
2018 Oct 28
0
[PATCH nbdkit 4/4] Add floppy plugin.
...P (floppy->fat_entries * 4, CLUSTER_SIZE);
+
+ nbdkit_debug ("floppy: %" PRIu64 " FAT entries", floppy->fat_entries);
+
+ /* We can now decide where we will place the FATs and data region on disk. */
+ floppy->fat2_start_sector =
+ 2080 + floppy->fat_clusters * SECTORS_PER_CLUSTER;
+ floppy->data_start_sector =
+ floppy->fat2_start_sector + floppy->fat_clusters * SECTORS_PER_CLUSTER;
+ floppy->data_last_sector =
+ floppy->data_start_sector + floppy->data_clusters * SECTORS_PER_CLUSTER - 1;
+
+ /* We now have to go back and update the cluster number...
2016 Feb 26
2
[PATCH 1/5] fat: fix minfatsize for large FAT32
Hi Ady,
I won't comment on the reasons why the original computation was wrong,
but thanks for the detailed analysis.
On 2016.02.26 08:05, Ady via Syslinux wrote:
>> Thus we can finally get a formula for Fs that satisfies the above:
>>
>> Fs = (To - Rs + Nf * Cs) / ((Ss * Cs / Fe) + Nf) + 1
>
> I believe such formula is slightly inaccurate too.
>
> My
2018 Oct 28
6
[PATCH nbdkit 0/4] Add floppy plugin.
Add nbdkit-floppy-plugin, “inspired” by qemu's VVFAT driver, but
without the ability to handle writes.
The implementation is pretty complete, supporting FAT32, LFNs, volume
labels, timestamps, etc, and it passes both ‘make check’ and ‘make
check-valgrind’.
Usage is simple; to serve the current directory:
$ nbdkit floppy .
Then using guestfish (or any NBD client):
$ guestfish --ro
2019 Jan 02
0
[PATCH nbdkit v2 1/2] Annotate internal function parameters with attribute((nonnull)).
...te__((__nonnull__ (1, 2)));
#endif /* NBDKIT_XZFILE_H */
diff --git a/plugins/floppy/virtual-floppy.h b/plugins/floppy/virtual-floppy.h
index 5a50c62..d9111b0 100644
--- a/plugins/floppy/virtual-floppy.h
+++ b/plugins/floppy/virtual-floppy.h
@@ -223,11 +223,20 @@ struct virtual_floppy {
#define SECTORS_PER_CLUSTER 32
#define CLUSTER_SIZE (SECTOR_SIZE * SECTORS_PER_CLUSTER)
-extern void init_virtual_floppy (struct virtual_floppy *floppy);
-extern int create_virtual_floppy (const char *dir, const char *label, struct virtual_floppy *floppy);
-extern void free_virtual_floppy (struct virtual_floppy *floppy);
-...
2019 Jan 02
4
[PATCH nbdkit v2 0/2] Use of attribute(()).
v1 was here:
https://www.redhat.com/archives/libguestfs/2019-January/msg00008.html
In v2 I have provided two patches:
The first patch extends attribute((nonnull)) to most internal
functions, but not to the external API.
The second patch uses a macro so that attribute((format)) is only used
in the public API on GCC or Clang. At least in theory these headers
could be used by a C compiler which
2011 Nov 10
5
[PATCH v2] Add tune2fs command.
The changes since the previous patch:
- safe ADD_ARG macro for adding arguments to a fixed size stack array
- support for testing functions that return RHashtable, ie. tune2fs-l.
- add tests that set (tune2fs) and get (tune2fs-l) various parameters.
- only one 'intervalbetweenchecks' parameter (in seconds)
Rich.