Issue #1586 has been updated by tuxillo. Description updated Category set to Userland Status changed from New to Feedback Assignee deleted (0) Target version set to 3.8.0 % Done changed from 0 to 100
Hi, Tried the following: # newfs_hammer -L T1 -f /dev/vkd1s1a Volume 0 DEVICE /dev/vkd1s1a size 4.00GB initialize freemap volume 0 initializing the undo map (504 MB) --------------------------------------------- 1 volume total size 4.00GB version 6 boot-area-size: 8.00MB memory-log-size: 8.00MB undo-buffer-size: 504.00MB total-pre-allocated: 0.51GB fsid: e23fc6e1-989e-11e3-a03f-010162fc1594 NOTE: Please remember that you may have to manually set up a cron(8) job to prune and reblock the filesystem regularly. By default, the system automatically runs 'hammer cleanup' on a nightly basis. The periodic.conf(5) variable 'daily_clean_hammer_enable' can be unset to disable this. Also see 'man hammer' and 'man HAMMER' for more information. WARNING: The minimum UNDO/REDO FIFO is 500MB, you really should not try to format a HAMMER filesystem this small. WARNING: HAMMER filesystems less than 50GB are not recommended! You may have to run 'hammer prune-everything' and 'hammer reblock' quite often, even if using a nohistory mount. # mount /dev/vkd1s1a /mnt HAMMER(T1) recovery check seqno=000fbfff HAMMER(T1) recovery range 3000000000000000-3000000000000000 HAMMER(T1) recovery nexto 3000000000000000 endseqno=000fc000 HAMMER(T1) mounted clean, no recovery needed # df -h /mnt Filesystem Size Used Avail Capacity Mounted on T1 3.5G 176M 3.3G 5% /mnt # newfs vkd1s1a vkd1s1a: media size 4093.65MB Warning: Block size and bytes per inode restrict cylinders per group to 89. Warning: 712 sector(s) in last cylinder unallocated /dev/vkd1s1a: 8383800 sectors in 2047 cylinders of 1 tracks, 4096 sectors 4093.7MB in 23 cyl groups (89 c/g, 178.00MB/g, 22528 i/g) super-block backups (for fsck -b #) at: 32, 364576, 729120, 1093664, 1458208, 1822752, 2187296, 2551840, 2916384, 3280928, 3645472, 4010016, 4374560, 4739104, 5103648, 5468192, 5832736, 6197280, 6561824, 6926368, 7290912, 7655456, 8020000 # newfs vkd1s1a vkd1s1a: media size 4093.65MB Warning: Block size and bytes per inode restrict cylinders per group to 89. Warning: 712 sector(s) in last cylinder unallocated /dev/vkd1s1a: 8383800 sectors in 2047 cylinders of 1 tracks, 4096 sectors 4093.7MB in 23 cyl groups (89 c/g, 178.00MB/g, 22528 i/g) super-block backups (for fsck -b #) at: 32, 364576, 729120, 1093664, 1458208, 1822752, 2187296, 2551840, 2916384, 3280928, 3645472, 4010016, 4374560, 4739104, 5103648, 5468192, 5832736, 6197280, 6561824, 6926368, 7290912, 7655456, 8020000 # mount_hammer /dev/vkd1s1a /mnt HAMMER(T1) Illegal UNDO TAIL signature at 300000001f7ffff8 HAMMER(T1) recovery failure during seqno backscan HAMMER(T1) recovery complete Failed to recover HAMMER filesystem on mount kthread 0x800fc02700 syncer11 has exited mount_hammer: mount on /mnt: Input/output error Note it can't be mounted. This is latest master and (HAMMER version 6). Maybe I am missing anything in the test? Cheers, Antonio Huete ---------------------------------------- Bug #1586: HAMMER: you can mount_hammer a UFS that was a hammer fs before http://bugs.dragonflybsd.org/issues/1586#change-11742 * Author: lentferj * Status: Feedback * Priority: Normal * Assignee: * Category: Userland * Target version: 3.8.0 ---------------------------------------- If a partition contains a hammer fs and you newfs it to a UFS you can afterwards still mount it as hammer fs. You can even still run hammer info and write data on the partition (tried with dd). Redo the following: atom# newfs_hammer -L pgsql /dev/ad11s2d Volume 0 DEVICE /dev/ad11s2d size 146.48GB initialize freemap volume 0 --------------------------------------------- 1 volume total size 146.48GB version 2 boot-area-size: 64.00MB memory-log-size: 0.50GB undo-buffer-size: 152.00MB total-pre-allocated: 168.00MB fsid: 98d1b558-c09e-11de-81f0-0122685cfb53 NOTE: Please remember that you may have to manually set up a cron(8) job to prune and reblock the filesystem regularly. By default, the system automatically runs 'hammer cleanup' on a nightly basis. The periodic.conf(5) variable 'daily_clean_hammer_enable' can be unset to disable this. Also see 'man hammer' and 'man HAMMER' for more information. atom# newfs /dev/ad11s2d /dev/ad11s2d: media size 149993.15MB Warning: Block size and bytes per inode restrict cylinders per group to 89. Warning: 1748 sector(s) in last cylinder unallocated /dev/ad11s2d: 307185964 sectors in 74997 cylinders of 1 tracks, 4096 sectors 149993.1MB in 843 cyl groups (89 c/g, 178.00MB/g, 22528 i/g) super-block backups (for fsck -b #) at: 32, 364576, 729120, 1093664, 1458208, 1822752, 2187296, 2551840, 2916384, 3280928, 3645472, 4010016, 4374560, 4739104, 5103648, 5468192, 5832736, 6197280, [...] atom# mount_hammer /dev/ad11s2d /mnt atom# mount ROOT on / (hammer, local) devfs on /dev (devfs, local) /dev/serno/9SF12T4Y.s2a on /boot (ufs, local) /pfs/@@-1:00001 on /var (null, local) /pfs/@@-1:00002 on /tmp (null, local) /pfs/@@-1:00003 on /usr (null, local) /pfs/@@-1:00004 on /home (null, local) /pfs/@@-1:00005 on /usr/obj (null, local) /pfs/@@-1:00006 on /var/crash (null, local) /pfs/@@-1:00007 on /var/tmp (null, local) procfs on /proc (procfs, local) pgsql on /mnt (hammer, local) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account