Description of problem: If you try to set a UUID on a reiserfs volume: reiserfstune -u random /dev/something the program tells it was not compiled with uuidlib support. Version-Release number of selected component (if applicable): 3.6.21-2.fc12 How reproducible: Always Steps to Reproduce: 1. dd if=/dev/zero of=zzz count=100 bs=1M 2. mkfs.reiserfs -f zzz 3. reiserfstune -u random zzz Actual results: reiserfstune: Cannot set the UUID, uuidlib was not found by configure. Expected results: Should set the UUID. Additional info: reiserfs-utils SRPM missing libuuid-devel dependency?
Fedora 15 Alpha is also affected. Kernel: 2.6.38.2-9.fc15 # gdisk -l /dev/sdc GPT fdisk (gdisk) version 0.6.14 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdc: 3907029168 sectors, 1.8 TiB Logical sector size: 512 bytes Disk identifier (GUID): C7195AB9-71BF-4729-91FF-74374D255B8F Partition table holds up to 128 entries First usable sector is 34, last usable sector is 3907029134 Partitions will be aligned on 2048-sector boundaries Total free space is 1159762028 sectors (553.0 GiB) Number Start (sector) End (sector) Size Code Name 1 2048 209715200 100.0 GiB 0700 Linux/Windows data 2 209717248 838862847 300.0 GiB 0700 Linux/Windows data 3 838862848 2097154047 600.0 GiB 0700 Linux/Windows data 4 2097154048 2202011647 50.0 GiB 0700 Linux/Windows data 5 2202011648 2726299647 250.0 GiB 0700 Linux/Windows data 6 2726299648 2747271167 10.0 GiB 0700 Linux/Windows data # mkreiserfs /dev/sdc6 -l reiser-test -u 444555 mkreiserfs: Cannot set up the UUID, uuidlib was not found by configure. # mkreiserfs /dev/sdc6 -l reiser-test mkreiserfs 3.6.21 (2009 www.namesys.com) A pair of credits: Jeremy Fitzhardinge wrote the teahash.c code for V3. Colin Plumb also contributed to that. Nikita Danilov wrote most of the core balancing code, plugin infrastructure, and directory code. He steadily worked long hours, and is the reason so much of the Reiser4 plugin infrastructure is well abstracted in its details. The carry function, and the use of non-recursive balancing, are his idea. Guessing about desired format.. Kernel 2.6.38.2-9.fc15.x86_64 is running. Format 3.6 with standard journal Count of blocks on the device: 2621440 Number of blocks consumed by mkreiserfs formatting process: 8291 Blocksize: 4096 Hash function used to sort names: "r5" Journal Size 8193 blocks (first block 18) Journal Max transaction length 1024 inode generation number: 0 UUID: <no libuuid installed> LABEL: reiser-test ATTENTION: YOU SHOULD REBOOT AFTER FDISK! ALL DATA WILL BE LOST ON '/dev/sdc6'! Continue (y/n):y Initializing journal - 0%....20%....40%....60%....80%....100% Syncing..ok ReiserFS is successfully created on /dev/sdc6. # blkid [...] /dev/sdb5: LABEL="xxxxx-dataX" UUID="4336369f-bdde-4b56-ac7b-445bc9464d36" TYPE="reiserfs" /dev/sdc6: LABEL="reiser-test" TYPE="reiserfs" # mkreiserfs /dev/sdc6 -l reiser-test -u 15f8a714-b12e-4026-add9-22704b8b9999 mkreiserfs: Cannot set up the UUID, uuidlib was not found by configure. For example, sdb5 is a reiserfs filesystem created under Slackware ??? before even migrating to Fedora.
Any chances for it comming in F16?
Verified still broken in F16.
Still present in F17. Come on people... Maybe I'm missing something, but this should be very easy to fix. It's kinda embarrassing that such a basic and essential thing (if you use reiser) doesn't work. Sorry for ranting, but I needed to say that ;)
With a low priority, I don't really expect them to fix it unless someone not on project opts to do so and then push the changes.
I do agree that this might be low priority, but this was filed against F14. The version field should be changed to either F16 or F17. Maybe a 'feature request' might be needed for F18? Otherwise F18 will be released also with this 'small' issue.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
fixed in rawhide, f18,f17,f16
reiserfs-utils-3.6.21-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/reiserfs-utils-3.6.21-6.fc17
reiserfs-utils-3.6.21-7.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/reiserfs-utils-3.6.21-7.fc18
reiserfs-utils-3.6.21-5.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/reiserfs-utils-3.6.21-5.fc16
reiserfs-utils-3.6.21-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
reiserfs-utils-3.6.21-5.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
Works in F17 stable, thanks!
reiserfs-utils-3.6.21-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.