New answers tagged solaris
You're expecting a JBOD, but it appears that this might be set up as a SAN, and you're seeing LUNs. You should check the 6140s themselves.
By default, on a dns serial change, the BIND master will notify all name servers defined in the NS records for the zone. From there, the slaves will contact the master to initiate a zone transfer.
You have to change the serial value to send a notification to all your slave servers telling them that the zone just changed so they can get the update. Here follows the meaning of these items: ttl: default time-to-live for cached entries, defines how long those entries should be considered fresh; refresh: the time used by slave to check for updates on ...
The statistics reported by df are obviously bogus. The root cause is likely a Solaris 10 df bug that was fixed around eight years ago. You should make sure you are up to date with patches !
The df command uses the statfs system call to find out the actual status of the filesystem usage. This statfs system call uses the actual filesystem driver of the given filesystem, which uses this information from the filesystem metadata on the hard disk. I am nearly sure, that your problem is that this filesystem metadata on your hard disk is broken. In ...
Ended up booting into a different Boot Environment through GRUB and copying the file from the old boot environment into my current corrupted one: beadm mount 'bootenviroment name' /a mv /a/kernel/drv/amd64/ixgbe ixgbeBAD cp /kernel/drv/amd64/ixgbe /a/kernel/drv/amd64/ixgbe beadm umount 'bootenviroment name'
Try booting with -B disable-ixgbe=true. Here's more on adding kernel arguments in GRUB: http://docs.oracle.com/cd/E26502_01/html/E28983/glyas.html
Top 50 recent answers are included