Search results

What you want to do is similar to Beeblebrox in create-pre-cloned-interface-for-virtualbox.50421. devd can execute actions in response to devices being added or removed. PF provides anchors as placeholders for rulesets that can then be changed dynamically; look at the pf.conf and pfctlman pages.

I would say it's better to get into the habit of using shutdown but I doubt that is causing your issue. I just looked at the source code for the ZFS rc.d script, which essentially runs zfs mount -a. I'm not sure why your pools are being forgotten, so the best I can offer is an ugly workaround...

I am sure the port maintainers would be grateful to learn about your research and receive any patches you are able to prepare. Have a look at the Dealing with Broken Ports section in the handbook.

MorgothV8, tobik is correct. You are using the AES-NI instructions on your CPU. From your dmesg output: [...] GEOM_ELI: Device ada0s1d.eli created. GEOM_ELI: Encryption: AES-XTS 256 GEOM_ELI: Crypto: hardware [...] GEOM_ELI: Device ada0s1b.eli created. GEOM_ELI: Encryption: AES-XTS 128...

Let's assume your ZFS cachefile is fine and not causing the issue. I had problems relating to the cachefile on FreeBSD 9.2 where the cachefile was needed to mount the root ZFS pool on the GELI container. That is likely why it was mentioned in the guide you read. However, I have had no issue...

Welcome to the forums dksayers. Since you are using development versions (see also topics-about-unsupported-freebsd-versions.40469) of both FreeBSD and Poudriere on a developmental architecture you might have better luck getting an answer on one of the mailing lists or on the IRC channel...

A third thought: Note that /boot needs to be a symbolic link to /uboot/boot for things to end up in the right place.

Two thoughts for things to try: Firstly, the man page for zdb says of the -C argument: Since it explicitly mentions the cachefile as being at /etc/zfs/zpool.cache it might be worth using the -U option to explicitly check your cachefile. Secondly, since the cachefile is currently located in a...

Hi trumee. I can't see the issue you describe in that post. The first line creates a GPT paritioning scheme. The second line adds a partition of type freebsd-zfs (note this will actually later be formatted as a GELI container) with the GPT partition label zstore, 4Kb sector alignment...

I'm pleased you're up and running. Matched disks are great though be quick if one fails as the others from the same batch may not be far behind :) Since the issue you have now (network/iSCSI/ZFS performance) is very different from the original issue in the thread title I suggest starting a new...

I had a thought that your issue might be much simpler. Did you remember to add zfs_enable="YES" to /etc/rc.conf? From the rc.conf man page:

The short answer is that I recommend using partitions. I had exactly the same question about whether to use whole disks or partitions when I first started using ZFS. You will have seen the web is full of people asking the question. Fortunately, FreeBSD is awesome when it comes to...

ZFS on FreeBSD doesn't support encryption natively. However, it is possible to create an encrypted container using GELI (see the geli man page) and then create the ZFS pool that uses the encrypted container or multiple encrypted containers. When you did your first install, the installer did...

I'm afraid I set up my network shares with a mixture of NFS and Samba before iSCSI was supported by ZFS on FreeBSD (from 10.0 I believe) so I don't have any experience with it though I see there is a section on iSCSI in the FreeBSD handbook. Someone else reading this on the forum may be able to...

mb2015, you could achieve a graceful shutdown by creating a script that fits with the rc framework. Have a look at this article: Practical rc.d scripting in BSD. Something like Neffi's script (that isn't currently compatible with the framework) above would be the code in the start() function...

I realised I didn't address your auto-mounting pools issue. Whether datasets in ZFS pools are automatically mounted is a setting in the pool, dataset or during the import. What I think you mean, though is that the pools aren't being imported. I had an issue like that with FreeBSD 9.2 but not...

Great. I'm assuming the gpart output is from booting without the additional drives plugged in based on your first post. If you want to keep the encryption you can: Boot without the additional drives plugged in Change the GELI settings in loader.conf to use the designations the drives will...

I'm pleased you found it helpful and thank you for the correction. bootfs is indeed a property of the pool not a dataset within it.

grep2grok, apologies that the start of my reply yesterday was unintentionally a little abrupt. While you gather the information let me offer some thoughts on the second part of your question. I noticed the specification sheet for your system says "Chassis supports up to five internal drives in...

Your immediate issue is your data rescue, so I'm going to totally ignore the second question in your thread. It sounds like your issue is with the decryption rather than ZFS. For your encryption I imagine you are using GELI. It sounds like you used the FreeBSD installer to configure your...