Search results

In comparison, here is an ZFS NAS with only 8GB of RAM with an L2ARC. http://pastebin.com/1Qai62iQ

As a follow up, I find it ironic that I was performing an update from 9.0-RELEASE to 9.0-p4 (as per freebsd-update fetch output)... and upon restarting the system, the output in uname -a states that the system is running at 9.0-p3, not p4.

I am also experiencing the same symptoms where the reboot process hangs at All buffers synced, but this is on a physical machine. I am able to get to this stage as I re-installed my FreeBSD box so that I can have ZFS on root, from the HOWTO below...

I purchased a SATA controller with the same chip, this also works under 8.2-RELEASE Here is the link for the controller http://www.sybausa.com/productInfo.php?iid=1104

I tried to search to see if the Marvell 88SE6320 SAS controller would be supported now, or in the future releases, but I came up empty. I know this is reviving an old thread, however how can I assist you with obtaining the necessary documentation for you to write drivers for the controller...

What command did you issue to receive that message??

I am able to reproduce the problem, even if the ZFS partition/pool has been created under FreeBSD. It's a strange problem. When I'm copying all of the contents on the USB drive (a ZFS pool) to my ZFS array on the same machine, it crashes. For example, issuing this command gives the "...

Thanks for your suggestion, unfortunately I took a different path since I am quiet uneasy to make changes on the FreeBSD kernel. I have not sat played around with FreeBSD enough to go that far, and time for me is difficult to find unfortunately. Instead, what I have done is destroyed the...

I'm a little stuck: plutonium# cd /usr/src plutonium# patch < /root/patch-2.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- stable/8/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c Wed Sep 15 16:05:51 2010...

Hello, I am currently running FreeBSD 8.1 amd64 and I would like to apply a .diff patch to repair a ZFS bug. Basically, I'm trying to copy a bunch of files from a ZFS v3/Zpool v14 pool created in Solaris. Problem is that the FreeBSD box hangs when attempting to copy files, and outputs a "...

I would also highly suggest labelling your hard-drives as well. A good naming scheme would be using manufacture and last few characters of the hard-drive serial number, such as what I've done below: $ zpool status pool: TANK state: ONLINE scrub: scrub completed after 5h16m with 0 errors...

The test was aimed for FreeBSD, but would be nice for the test to include ZFS on OpenSolaris as well.

How did you access the ZFS pool via Samba and NFS? I was under the impression that those filesharing protocols in ZFS were removed in FreeBSD, but I see you enabled them (or tried to) in ZFS? Am I wrong?? EDIT: According to the site below, NFS can be enabled from ZFS but Samba needs to be...

I am currently using the Asus P6T6 WS Rev. (Intel X58 chipset) since FreeBSD 7.2 . No issues, although some components on the motherboard (mainly the Marvell SAS controller) do not have drivers for them at this time. Otherwise, its working without problems...

$ dmesg | grep -i realtek re0: <RealTek 8168/8168B/8168C/8168CP/8168D/8168DP/8111B/8111C/8111CP/8111DP PCIe Gigabit Ethernet> port 0xe800-0xe8ff mem 0xfbeff000-0xfbefffff,0xf7ef0000-0xf7efffff irq 17 at device 0.0 on pci11 re1: <RealTek...

I wonder if we should justify using sync(8) for these tests?

I have 2 zpool's on my system and I have no issues participating in these tests. As long as the commands used is all laid out, then I'll post my results and we can compare. My results will be skewed as I have enabled compression globally on all of my pools (using lzjb compression), but the...

Is there any compression enabled or changes to checksum algorithms on your zpool's ?

If you noticed on my TANK zpool, there is a "TB_SPARE" drive. All those drives in that zpool are 1TB drives, and I happened to have a spare 1TB drive laying around to use as a substitute when I start labelling my drive. It is connected via USB. The procedure I'm using is the following: 1 -...

I've experienced the exact same issue earlier this week, until I read around and realized the existence of glabel. The basic purpose of labels is to simply have a hard-drive labeled to your likings, and having FreeBSD "follow" that labeled hard-drive regardless of which I/O or JBOD controller...