From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sage Weil Subject: Re: feature request to "ceph osd status" Date: Wed, 30 Aug 2017 13:52:54 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60418 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751318AbdH3Nwz (ORCPT ); Wed, 30 Aug 2017 09:52:55 -0400 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Two Spirit Cc: John Spray , Ceph Development On Tue, 29 Aug 2017, Two Spirit wrote: > I found "ceph pg dump" also gives the same OSD disk usage information. > It has summary row, as well as 3 columns. > The bad thing is that the numbers in ceph pg dump and ceph osd status > do not match. I'm guessing someone isn't dividing by 1024. > I think for consistency the PG stuff should go under ceph pg, and OSD > info go under ceph osd. On my test box it matches (current master): OSD_STAT USED AVAIL TOTAL HB_PEERS PG_SUM PRIMARY_PG_SUM 0 274G 98.4G 372G [] 0 0 vs $ df -h . Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1 373G 274G 99G 74% /nvm > As an IT person, I like to to write perl scripts around the outputs, > and so persistence of the output format is desired FWIW you should *never* script against the plaintext output, as it is more like to change (for readability or other reasons... e.g., changing a raw byte count to something like "98.4G"). Use the structured JSON or XML output with -f json[-pretty] or -f xml[-pretty]. sage > > On Tue, Aug 29, 2017 at 2:50 PM, Two Spirit wrote: > > I agree the information is redundant, but when I'm trying to figure > > out what is going on, it is very nice to have all info right in front > > of my face instead of uber bare bones. Running 'df -kh' shows [Total] > > Size, Used, Avail and Use%. That is one step past redundant, but it is > > aweful nice to see whatever information I want quickly as well as in a > > familiar format and bit of info I think unix it guys are use to. I can > > pick the columns of information I need based on what I'm trying to > > debug. just my two bits on a feature request. > > > > On Mon, Aug 28, 2017 at 5:01 AM, John Spray wrote: > >> On Sat, Aug 26, 2017 at 7:07 PM, Two Spirit wrote: > >>> Hi. I found this command by accident. it doesn't seem to be undocumented. > >>> > >>> ceph osd status > >>> > >>> There is a very similiar command "ceph osd stat" with different info > >>> > >>> The status command is very useful command and I'd like to see it stay > >>> around even tho it seems to be an undocumented command. > >>> > >>> It would be nice to have a 3rd column "total" which is used+avail > >>> columns and then another row at the bottom subtotaling the "used", > >>> "avail", and "total" columns. > >> > >> I prefer to pick two of avail/used/total, rather than printing all > >> three -- otherwise the information is a bit redundant. > >> > >> Putting some totals at the bottom is an interesting idea though. The > >> "osd status" and "fs status" commands are implemented in a python > >> module[1], so anyone who knows a little python could add that. > >> > >> John > >> > >> 1. https://github.com/ceph/ceph/blob/master/src/pybind/mgr/status/module.py > >> > >>> > >>> I know all these could be be calculated, but with more OSDs, it is > >>> convenient to have it all available at a glance > >>> -- > >>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > >>> the body of a message to majordomo@vger.kernel.org > >>> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >