-
huyHello, I just restarted a native zone and everything's very slow, what should I check?
-
toastersonprstat, memory usage, and iostat
-
huy1453.9 w/s is a lot ?
-
toastersondepends
-
toastersonwe can't really tell you unless you show the whole output
-
huy
-
toastersonit's doing things. so if the service is slow it's more likely a service thing. But debugging this is the same as on any other unix/linux system
-
huyOk, thanks toasterson
-
huythe system was slow to startup too though
-
toastersonWell, the only way to debug any performance problem is to narrow it down to the cause same as in linux and then go from there. There is no magic tool unless you have narrowed down the issue
-
huyOk, thanks
-
bahamathuy: You very obviously have *something* very busily writing to disk. The next step is to figure out *what* that is.
-
bahamatAs to whether or not *that* is what's affecting your performance, it depends on a great many things. It's impossible for us to say.
-
bahamatIf you have two 5400 RPM HDDs, then maybe, yeah, 1500 w/s would do it. If you have 5x11 nvme raidz pool, then 1500 w/s then probably not.
-
neuroservehuy : are there any zones started already? maybe "prstat -Z" can help to narrow down which one is writing
-
huyneuroserve: there's about a dozen other zones, there was one writing a lot but the affected one it the only one to exhibit this behavior
-
danmcd@Smithx10
-
danmcdWould stuff interface #: 1
-
danmcd[ERROR] in config file: invalid location_data_format '0'
-
danmcdAnd `Unable to dlpi_bind ixgbe0: Device busy` is interesting, as if LLDP is already running?
-
danmcdOh NVM about the location_data_format, that's expected noise.
-
danmcdI am running lldp on untrunked ixgbe just fine. the EBUSY you're seeing suggests maybe it's already running?
-
danmcd`pgrep lldp` ?
-
Smithx10
-
danmcdSo restart lldp?
-
danmcdOooh actually before you do that.
-
danmcd`pfiles 348589`
-
danmcdand `gcore 348589`
-
Smithx10