A couple things that I've discovered over time that might help:
Don't ever use the root user for zpool queries such as "zpool status". If you
have a really bad failing disk a zpool status command can take forever to
complete when ran as root. A "su nobody -c 'zpool status'" will return results
On Thu, 22 Jun 2017, Schweiss, Chip wrote:
I'm talking about an offline pool. I started this thread after rebooting
a server that is part of an HA pair. The other server has the pools
online. It's been over 4 hours now and it still hasn't completed its disk
scan.
Every tool I have that
Hi,
Certain commands (in particular during attach) are send by mptsas itself,
these have a timeout set in the driver and are not issued by SD hence these
commands are not affected by changing those values. See for example,
mptsas_access_config_page()
- Jeffry
On Thu, Jun 22, 2017 at 10:12 PM,
I'm talking about an offline pool. I started this thread after rebooting
a server that is part of an HA pair. The other server has the pools
online. It's been over 4 hours now and it still hasn't completed its disk
scan.
Every tool I have that helps me locate disks, suffers from the same
Have you able to and have tried offlining it in the zpool?
zpool offline thepool
I'm assuming the pool has some redundancy which would allow for this.
/dale
> On Jun 22, 2017, at 11:54 AM, Schweiss, Chip wrote:
>
> When ever a disk goes south, several disk related takes
On Thu, Jun 22, 2017 at 11:05 AM, Michael Rasmussen wrote:
>
> > I thought this /etc/system setting would reduce the timeout to 5 seconds:
> > set sd:sd_io_time = 5
> >
> I think it expects a hex value so try 0x5 instead.
>
>
Unfortunately, no, I've tried that too.
-Chip
> --
On Thu, 22 Jun 2017 10:54:25 -0500
"Schweiss, Chip" wrote:
> I thought this /etc/system setting would reduce the timeout to 5 seconds:
> set sd:sd_io_time = 5
>
I think it expects a hex value so try 0x5 instead.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG