summaryrefslogtreecommitdiffstats
path: root/tests/expected/blkid
Commit message (Collapse)AuthorAgeFilesLines
* tests: update fdisk outputsKarel Zak2019-02-121-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* Removed BlueStore VERSION information as it is gibberishKenneth Van Alstyne2018-12-181-1/+0Star
|
* Updated BlueStore expected resultKenneth Van Alstyne2018-12-171-0/+1
|
* Added BlueStore test imageKenneth Van Alstyne2018-12-171-0/+2
|
* tests: add test images for drbd v08/v09Roland Kammerer2018-11-292-0/+10
| | | | | | | This adds DRBD meta data images for DRBD versions 8 and 9, as well as the according expected output. Signed-off-by: Roland Kammerer <roland.kammerer@linbit.com>
* tests: update fdisk outputKarel Zak2018-08-301-0/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: update fdisk dialogsKarel Zak2018-07-313-6/+6
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* libblkid: udf: Fix reporting UDF 2.60 revisionPali Rohár2018-05-251-0/+10
| | | | | | | | | | | | | According to the UDF 2.60 specification, the Minimum UDF Read Revision value shall be at most #0250 for all media with a UDF 2.60 file system. So in this case use Minimum UDF Write Revision as ID_FS_VERSION to distinguish between UDF 2.50 and UDF 2.60 discs. This commit also adds a testing Blu-Ray Recordable image with UDF revision 2.60 created by Nero which really sets Minimum UDF Read Revision to 2.50. Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
* Merge branch 'master' of https://github.com/pali/util-linuxKarel Zak2018-03-2721-0/+134
|\ | | | | | | | | | | | | * 'master' of https://github.com/pali/util-linux: tests: Add tests for FAT32 labels blkid: Encode any field which starts with LABEL in same way as LABEL field libblkid: vfat: Change parsing label in special cases
| * tests: Add tests for FAT32 labelsPali Rohár2017-11-2521-0/+134
| | | | | | | | | | | | | | | | | | | | These FAT32 images were generated for FAT label test suite in October 2017. Now blkid reports same FAT32 label as MS-DOS 6, 7 and Windows 98, XP, 10. For more information about test result see email: https://www.spinics.net/lists/kernel/msg2640891.html Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
* | tests: add mpool blkid test imageKarel Zak2018-02-051-0/+6
| | | | | | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* | tests: added test for libblkid atari ptVaclav Dolezal2018-01-232-0/+16
| | | | | | | | Signed-off-by: Vaclav Dolezal <vdolezal@redhat.com>
* | libblkid: Add VDO superblock information into blkidSweet Tea Dorminy2017-12-071-0/+4
|/ | | | | | | [kzak@redhat.com: - add tests/expected/blkid/low-probe-vdo - enlarge the image (must be > 1024)] Signed-off-by: Karel Zak <kzak@redhat.com>
* libblkid: udf: Fix parsing UDF revisionPali Rohár2017-11-201-0/+10
| | | | | | | | | | | | | | | | | UDF revision is stored as decimal number in hexadecimal format. E.g. number 0x0150 is revision 1.50, number 0x0201 is revision 2.01. Apparently all UDF test images have number which has same representation in decimal and hexadecimal format, so problem was not detected. This patch adds new test image with UDF revision 1.50. Internally number is stored as 0x0150. In decimal format it is (incorrectly) 1.80, but in hexadecimal correct 1.50. $ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-8.img bs=1M count=10 $ mkudffs -r 0x150 -b 512 udf-hdd-mkudffs-1.3-8.img Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
* tests: Add UDF cd image created by mkudfiso 20100208Pali Rohár2017-11-161-0/+7
| | | | | | | | | $ mkudfiso -v "Volume Label" . | tail -n +2 > udf-cd-mkudfiso-20100208.img mkudfiso 20100208 creates UDF images without valid LVID (and LVIDIU), so it is a good candidate for testing fallback code for ID_FS_VERSION. Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
* Merge branch 'udf' of https://github.com/pali/util-linuxKarel Zak2017-11-131-0/+10
|\ | | | | | | | | | | * 'udf' of https://github.com/pali/util-linux: test: Add UDF hdd image with final block size 4096 created by Linux mkudffs 1.3 libblkid: udf: Optimize and fix probing when block size > 2048 bytes
| * test: Add UDF hdd image with final block size 4096 created by Linux mkudffs 1.3Pali Rohár2017-11-121-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | $ dd if=/dev/zero of=udf-hdd-mkudffs-1.3-7.img bs=1M count=10 $ mkudffs -l Label512 -b 512 udf-hdd-mkudffs-1.3-7.img $ mkudffs -l Label4096 -b 4096 udf-hdd-mkudffs-1.3-7.img Image file was first formatted with block size 512 and then reformatted with block size 4096. Volume Recognition Sequence was overwritten and every Volume Structure Descriptor is now 4096 bytes long. Trying to read second VSD as 2048 bytes long will fail because 4069 bytes long VSD is padded with zeros. To verify that image file was properly detected, it should have label "Label4096" and not "Label512".
* | libblkid: vfat: Fix reading labels which starts with byte 0x05Pali Rohár2017-11-091-0/+7
|/ | | | | | | | When FAT directory entry has leading byte 0x05 it is interpreted as byte 0xE5. This is how FAT stores file name which starts with byte 0xE5 as leading byte in 0xE5 in FAT directory entry means that file slot is empty. Fixes: #533
* tests: add LUKS test imagesMilan Broz2017-10-242-0/+13
| | | | | | | Testing image contains only the first 4k sector, so it is not valid, but for blkid it should be enough. Signed-off-by: Milan Broz <gmazyland@gmail.com>
* libblkid: mark UBI as RAIDKarel Zak2017-08-031-1/+1
| | | | | | | | | UBI is volume manager rather than filesystem. Note that libblkid has optimized RAIDs probing (don't search for another filesystems is RAID detected). We also don't search for RAIDs on very small devices, but this optimization is ignored for UBI char devices (size=1byte). Signed-off-by: Karel Zak <kzak@redhat.com>
* libblkid: add support for UBI superblockRafał Miłecki2017-08-031-0/+5
| | | | | | | | | | | | | | | | | | UBI is a volume management system that can be used on a raw flash partition for providing multiple logical volumes. Detecting UBI superblock may be useful for tools wanting to simplify or automate attaching UBI. Please note it's not directly related to the ubifs support which is just a filesystem working on top of UBI volume. In other words: UBI can be used on MTD partition (e.g. /dev/mtdblock0) while ubifs can be used on UBI volume (e.g. /dev/ubi0_0). This patch adds simple code reading UBI version and unique number and setting it in the blkid_probe. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* tests: update UDF test, add ID_FS_VERSIONPali Rohár2017-07-0513-0/+13
|
* tests: Add UDF hdd image which label has length 30 charactersPali Rohár2017-06-221-0/+9
| | | | | | | | | | 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
* tests: Add UDF hdd images with blocksize 1024 and 4096 created by Linux ↵Pali Rohár2017-06-142-0/+18
| | | | | | | | | | 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
* tests: Fix UDF test output after changing UUID algorithmPali Rohár2017-05-176-12/+12
|
* tests: Fix UDF test output for 8bit OSTA Compressed UnicodePali Rohár2017-05-161-1/+1
|
* tests: Add UDF hdd image with non ASCII 8bit label created by Linux mkudffs 1.3Pali Rohár2017-05-161-0/+9
| | | | | $ 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
* tests: Add UDF CD-ROM hybrid image (ISO+Joliet+UDF) created by Nero 6Pali Rohár2017-05-051-0/+9
| | | | | | | | | | | | | | | | | | | 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.
* tests: Fix test output for low-probe-udf to contain UDF dataPali Rohár2017-05-051-5/+2Star
| | | | | | | | | 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.
* tests: Add UDF hdd images created by Linux mkudffs 1.3Pali Rohár2017-05-012-0/+18
| | | | | | | | $ 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
* tests: Rename udf-hdd-mkudffs* images to indicate used mkudffs versionPali Rohár2017-05-012-0/+0
|
* test: fix raid1 minimum I/O sizeRuediger Meier2016-10-211-1/+1
| | | | | | | 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>
* tests: add DM error target for blkidKarel Zak2016-03-301-0/+4
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: ts_fdisk_clean(), remove optimal iosizeRuediger Meier2016-02-103-3/+3
| | | | | | | | 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>
* tests: update ZFS testKarel Zak2015-11-191-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: (blkid) update drbdmanageKarel Zak2015-08-311-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* libblkid: added drbdmanage control volume detection.Philipp Marek2015-08-241-0/+5
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: add blkid script to test whole-disk MBR devicesKarel Zak2015-08-211-0/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: Add UDF hdd image created by NetBSD newfs_udf (from UDFclient 0.7.7)Pali Rohár2015-01-081-0/+9
| | | | | | | $ 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.
* tests: Add UDF hdd image created by NetBSD newfs_udf (from UDFclient 0.7.5)Pali Rohár2015-01-081-0/+9
| | | | | | | | $ 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.
* tests: Add UDF hdd image created by Linux mkudffs with custom paramsPali Rohár2015-01-081-0/+9
| | | | | | | | | | $ 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!
* tests: Add UDF hdd image created by Linux mkudffsPali Rohár2015-01-081-0/+9
| | | | | $ dd if=/dev/zero of=/tmp/test bs=1M count=10 $ mkudffs -b 512 /tmp/test
* tests: Add UDF hdd image created by Windows 7Pali Rohár2015-01-081-0/+9
|
* tests: update UDF test (add identifiers)Pali Rohár2014-12-151-0/+3
|
* tests: update fdisk formattingKarel Zak2014-10-143-3/+0Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* fdisk: update tests and clean up outputKarel Zak2014-08-083-0/+3
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: refresh fdisk outputsKarel Zak2014-03-113-36/+24Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: fdisk now prints SGI system partitions tooKarel Zak2014-02-171-0/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: update blkid swap testsKarel Zak2013-11-082-2/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* tests: update fdisk outputsKarel Zak2013-10-083-3/+3
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>