From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sage Weil Subject: Re: scubbing for a long time and not finished Date: Thu, 19 Mar 2015 06:33:30 -0700 (PDT) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ceph-users-bounces-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org Sender: "ceph-users" To: Xinze Chi Cc: "ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org" , "ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: ceph-devel.vger.kernel.org On Thu, 19 Mar 2015, Xinze Chi wrote: > Currently, users do not know when some pg do scrubbing for a long time. > I think whether we could give some warming if it happend (defined as > osd_scrub_max_time). > It would tell the user something may be wrong in cluster. This should be pretty straightforward to add along with the other "stuck x" warnings based on the pg_stat_t state timestamps. On the otherhead, that may be a somewhat heavyweight approach (each new warning bloats the stat structure a bit); open to other ideas! sage