Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
rpool is on a 2TB drive and shows 2% capacity
edit: running zdb -emm tank results in the following:
http://i.imgur.com/19VLuf5.png
running the same command on rpool completes successfully
edit2: got it up and running with the pool mounted in readonly... think it may have suffered this bug...
Solaris 11 server crashed this evening, now on boot the following error appears:
http://i.imgur.com/cqZG6KC.png
Anyone seen this before? I have no idea what it means...
Edit: I can boot into maintenance mode, and can force this crash just by typing zpool status :(
I use monowall on both sides, one side already being virtualized on significant hardware. Best I can tell, neither side is cpu bottlenecked, and the issue is some kind of software bottleneck with regard to encryption speed. I can make major changes such as moving both to hardware with a crypto...
I'd like to create an appliance group for replication, but I'd like them to communicate over the internet. The reason for this is to overcome a bottleneck with our IPSEC vpns that limit replication speed to ~20Mbps.
Will this work, and what are the implications regarding firewall ports...
Thanks Gea, you've clarified a few things for me. I was messing with the timeouts in the job script, and after setting it as follows, the replication completed properly:
my $src_interface = "sudo /usr/bin/nc -w 60 10.0.0.139 57463";
my $dest_interface = "sudo /usr/bin/nc -w...
I'm trying to set up a few replication jobs that will run over a 5Mb uplink. The first folder I'm replicating is 32GB, but the initial replication will never properly complete. It will appear to progress fine for 10 hours or so, then I'll check it and it shows no error, but the replicated...
There's a bug/design flaw in napp-it that takes the dns entry you input for your domain server and replaces the ip in resolv.conf with that dns name. You'll need to place the ip in resolv.conf again and run the last step manually.
You can use this page, check each step to verify and you...
Mind elaborating here? Is this something where we can add a new variable into the current job script, or recreate but use the same snapshot pair? Will current jobs break with the update, or just not include the fix?
On a 1.4TB ZFS folder, I scheduled a replication job. On it's first run, it proceeded to somewhere around 64%, then the progress reversed iteself, counting down the percentage and the job finished without presenting an error. The target ZFS folder showed no data.
Immediately running the job...
Here is what I have done, which *appears* to work:
I have job 1306722125, which replicates a ZFS folder from host-a to host-b.
host-b has an ip address change.
1. host-b appears offline on host-a under extensions-appliance-group. Remove host-b and re-add with the new ip address.
2. Test...
You're correct re: disk-smartinfo; it's there, just missed it because of the two different fields.
Didn't even have to edit the ABCD jobs, they're running now :)
Impressive. Do prior jobs using ABCD need to be recreated?
Edit: I also notice that Disks > Diskinfo now show serial#'s for drives connected to sas2008 controllers (under smart_sn, not sn). This is excellent! Not yet showing under Disks or Disks > Smartinfo, but as it is it makes things...