Search results

  1. S

    The use of 'make config' in scripted environments

    Thanks for suggesting Poudriere. However, I'm not looking to replace my current solution, which is probably more advanced than anything out there. It basically starts with downloading the sourcecode, and finishes with LiveCD and other produced stuff ready for upload to the master server. The...
  2. S

    The use of 'make config' in scripted environments

    Dear BSD users, I could use some help with the following. I'm working on a solution to automate port building for my project, ZFSguru. Previously I used scripts that do this semi automated, but now I'm working on a solution with full automation. The actual building of the ports works great...
  3. S

    ZFS metadata corruption

    In my experience the filename affected by corruption will disappear from the zpool status -v output once you delete the file. However, if one or more snapshots are still referencing this data, the name will disappear and an identifier is put in its place. That is why I recommended destroying...
  4. S

    4K Blocks and letting Zpool create a pool.

    Of course, 18 disks in RAID-Z2 is not recommended in general, for several reasons: 1) many disks in one RAID-Z-like vdev means the entire vdev has the random I/O capabilities of just one disk; 2) 2 disks parity may be too few for 18 disks total; using 2 RAID-Z2 of each 10 disks would be more...
  5. S

    ZFS metadata corruption

    Remove the snapshots holding those data references. Then use zpool clear to clear the errors.
  6. S

    4K Blocks and letting Zpool create a pool.

    Two things required to work well with 4K sector emulation drives aka Advanced Format: proper alignment ashift=12 meaning ZFS will do I/O in multiples of 4KiB (4096 bytes). In your case you have optimized ZFS to use ashift=12 which is good. The alignment should also be good if you use raw disks...
  7. S

    What file system to use for FreeBSD guest in VirtualBox

    UFS is reliable and resilient?! Did I miss something? ;-) The only protections these so called 'legacy filesystems' provide is against loss of DRAM buffer in the storage device. They use journaling or soft-updates or similar solution to protect against inconsistencies in the filesystem metadata...
  8. S

    raidz strange capacity

    I would give a slightly more nuanced answer. ZFS can no longer protect your files when it loses its redundancy. If bad sectors were to occur at any of the remaining disks, this could lead to dataloss. However, thanks to ZFS employing ditto copies - aka copies=2 - for all ZFS metadata, this...
  9. S

    Disk spindown and APM/AAM settings

    Hello forum members, I'm working on a web-interface for FreeBSD+ZFS. This interface allow users to manage ZFS and one of the things I'm currently working on is spinning down disks and up again, setting APM (Advanced Power Management) and AAM (Automatic Acoustic Management). I currently know...
  10. S

    Is ia64 the same as amd64?

    I believe it has to do with the principle of "credit where credit is due". Intel designed the x86 instruction set, so i386 bares the 'i' from Intel. With AMD having designed the 64-bit extension to this instructionset and having it called AMD64; it's only consistent to call platforms on this...
  11. S

    Do I need to flash IT firmware when using ZFS with LSI?

    With IR (Integrated RAID) firmware, there could be the possilibility of detached (disconnected) disks if they encounter a bad sector causing them to have high timeouts. Many RAID controllers disconnect disks that spend more than 10 seconds on recovery time, not able to distinguish disks...
  12. S

    Compiling rtorrent from ports fails

    Managed to solve the problem by recompiling everything that I recompiled earlier using GCC 4.4.x. With base GCC and default /etc/libmap.conf and /etc/make.conf it worked; but I had to recompile some dependencies first. Thanks for your help!
  13. S

    Compiling rtorrent from ports fails

    Thank you, will try that. I did that because the author of rtorrent said that GCC 4.1.2 could be the problem, in response to someone with the same compile errors. I guess now that I updated to 8.2, I should use the base GCC again. Going to try that now.
  14. S

    Compiling rtorrent from ports fails

    Hi guys, I've been running rtorrent 0.86_1 or something I believe, on an older FreeBSD 8.0 i386 machine. At one point an update was available (0.87) - but compiling that using portupgrade failed. During my attempts to solve the problem, I made a bad decision to remove the currently installed...
  15. S

    zfs +cache taking too much ram

    You described very accurately of what I believe should be done. Even better would be run-time configurable limits via sysctl. The workaround for now would be a 100% ZFS system with Root-on-ZFS. Both the mfsBSD and ZFSguru projects have .iso images that can perform a Root-on-ZFS installation.
  16. S

    [FreeNAS] Bad superblock on gconcat device

    I'm missing the 'gconcat status' output? Also, any partitions on the concat device? ls -l /dev/concat/* If you want geom_concat available from your livecd, then load the kernel module first: kldload geom_concat
  17. S

    Mysterious issue involving GPT and ZFS

    Well that's just it, they were BOTH corrupted! I know how GPT complains if only the second was missing somehow, which can occur if the device suddenly grew in size so that of course the last sector has changed, then you will get such a message. But in my case, both GPT labels were corrupted...
  18. S

    Mysterious issue involving GPT and ZFS

    Good feedback danbi, thanks! Your idea about ZFS v28 having more tricks at its sleeve regarding offset/geom/geometry might be a reason why ZFS v28 can use it without problems. After the GPT label problems, I wrote a new (identical) label, this process: - writes zeroes to the first 1MiB of the...
  19. S

    Mysterious issue involving GPT and ZFS

    I first read the entire raw disk to a single file using dd, I then restored the GPT partition by re-creating it. I noticed with 'cmp' that this did cause some changed values, but only a few bytes. This would suggest the label was indeed corrupted. If wrong/bad metadata was written due to a bug...
  20. S

    Mysterious issue involving GPT and ZFS

    Even if that were true, that still does not explain corruption of the primary GPT table at the begin of the disk, where geom_label does not touch anything. The link you gave me uses poor alignment, and is not related to my issue. He uses GEOM labels which wouldn't work and produced error output...
Back
Top