linux-kernel - pNFS client behavior confirmation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <955256583.2570604.1402504421889.JavaMail.zimbra@desy.de>
Date:	Wed, 11 Jun 2014 18:33:41 +0200 (CEST)
From:	"Mkrtchyan, Tigran" <tigran.mkrtchyan@...y.de>
To:	Linux Kernel mailing list <linux-kernel@...r.kernel.org>
Cc:	Andy Adamson <william.adamson@...app.com>,
	Steve Dickson <steved@...hat.com>
Subject: pNFS client behavior confirmation

Dear pnfs developers,

I would like to confirm client behavior which was hurting us for years.

If for some reason the client is unable to connect to a DS, then this DS got blacklisted
and the only way to whitelist it again was client reboot. With RHEL7 (and I believe with
upstream kernel), after 2 mins client 'forgets' about bad DS and uses it again. This
behavior is tested and confirmed during June bakeathon.

Missing bits:

  i) it takes client 6 min to fall back to MDS, e.g time between LAYOUTGET and first WRITE to MDS 
  ii) there are no log entries why client have decided to use MDS

Thanks,
   Tigran.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/