| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Structure dstring for label has 32 bytes, first byte is 8 (Compression ID),
last byte is 30 (count of 8bit characters in label). Therefore label is not
nul terminated and dstring parser needs to handle it (fixed in previous
commit).
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-6.img bs=1M count=10
$ mkudffs -l AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA -b 512 udf-hdd-mkudffs-1.3-6.img
|
|
|
|
|
|
|
|
|
|
| |
mkudffs 1.3
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-4.img bs=1M count=10
$ mkudffs -l Label -b 1024 udf-hdd-mkudffs-1.3-4.img
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-5.img bs=1M count=10
$ mkudffs -l Label -b 4096 udf-hdd-mkudffs-1.3-5.img
|
| |
|
| |
|
|
|
|
|
| |
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-3.img bs=1M count=10
$ mkudffs -l 'ÿ' -b 2048 /tmp/udf-hdd-mkudffs-1.3-3.img
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This image was created by Nero Burning ROM version 6 via option CD-ROM
(UDF/ISO) with UDF version 2.01 and enabled ISO Joliet extension. Moreover
for testing purposes it has set custom Disc label (and also every other
identifier) which is different for ISO, Joiliet and UDF part. It contains
ISO/Joliet/UDF string prefix to distinguish between them.
So reading this image as basic ISO would produce different label as when
reading it as ISO with Joliet image and also different as UDF image.
Windows detects its label as "UDF Label".
Before commit ccfb5b0a1d318c1ac96884c70c7b5090331849fc blkid show label for
this image as "Joliet Label" and after as "UDF Label".
Note that it is not common to have such images with different label stored
in Joliet part and in UDF part. Moreover it is very hard to generate them.
|
|
|
|
|
|
|
|
|
| |
Label was really not changed because of fix by commit
2f2730bc77c972d613cfec421468c84f15749708.
UUID is different due to fact that ISO image does not have UUID and
libblkid generate one from compilation date. Plus "Joliet Extension" in UDF
context does not make sense.
|
|
|
|
|
|
|
|
| |
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-1.img bs=1M count=10
$ mkudffs -l Label -b 512 udf-hdd-mkudffs-1.3-1.img
$ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-2.img bs=1M count=10
$ mkudffs -l Label udf-hdd-mkudffs-1.3-2.img
|
| |
|
|
|
|
|
|
|
| |
Seems this has been changed in kernels >4.4.x or >4.8
from 512 bytes to 64K.
Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
|
|
| |
It's a pity a pity that we have to remove it. In past our test suite
could discover a kernel bug (4.4). But now they've changed optimal
iosizes on purpose.
Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
|
| |
$ dd if=/dev/zero of=/tmp/test bs=1M count=10
$ newfs_udf -L discname /tmp/test
Version from UDFclient 0.7.7 generate default Volume set identifier correctly.
|
|
|
|
|
|
|
|
| |
$ dd if=/dev/zero of=/tmp/test bs=1M count=10
$ newfs_udf -L discname /tmp/test
Version from UDFclient 0.7.5 does not generate default Volume set identifier
according to OSTA UDF specification. But it is used so for test is usefull.
|
|
|
|
|
|
|
|
|
|
| |
$ dd if=/dev/zero of=/tmp/test bs=1M count=10
$ mkudffs -b 512 --lvid=Label --vid=Label --vsid="Volume set identifier" /tmp/test
When calling mkudffs with --vsid param there is bug which cause that garbage
from application stack is copied into Volume set identifier after 8th character.
Characters 1 -- 16 are used in libblkid for generating UUID, so this is perfect
test example that everything is working!
|
|
|
|
|
| |
$ dd if=/dev/zero of=/tmp/test bs=1M count=10
$ mkudffs -b 512 /tmp/test
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
| |
images generated by Rolf Fokkens <rolf@rolffokkens.nl>
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
|
|
|
| |
- the new fdisk ask-partition-number dialog does not ask for non-senses
(non-existing partitions etc.)
- 'p'rint command prints disk label name (usually "dos" in the tests)
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
| |
.. blkid now returns infor from ISO header too.
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
|
|
| |
* count checksum from superblock
* new (correct) superblock definition from dmraid
Reported-by: Frank Hirtz <fhirtz@redhat.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Alejandro Martinez Ruiz <alex@nowcomputing.com>
|
|
|
|
|
|
|
|
|
|
|
| |
* tests/expected/blkid/mk-raid1-part: Replace major and minor number
of ID_PART_ENTRY_DISK by a special string. Add ID_FS_UUID and
ID_FS_UUID_ENC again, also with a special string.
* tests/ts/blkid/md-raid1-part: Before comparing the expected output
with the actual output, replace the values of ID_PART_ENTRY_DISK,
ID_FS_UUID and ID_FS_UUID_ENC with the speacial strings mentioned above.
Signed-off-by: Bernhard Voelker <mail@bernhard-voelker.de>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Francesco Cosoleto <cosoleto@gmail.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change enables the auto-detection of the internal storage on a VTech
Kidizoom camera, which has a zero head count value in the superblock.
Microsoft documentation, "FAT: General Overview of On-Disk Format", states
that the sectors and heads fields are only relevant for media that have
a geometry.
The Linux kernel also does not require a non-zero head count, and can
manually mount the filesystem.
Signed-off-by: Nick Holloway <Nick.Holloway@pyrites.org.uk>
|
|
|
|
| |
Signed-off-by: Karel Zak <kzak@redhat.com>
|