From: p_s_d_a_s_i_l_v_a_ns@netcabo.pt   
      
   Às 11:17 de 09-07-2018, Carlos E.R. escreveu:   
   > On 2018-07-09 07:40, Paulo da Silva wrote:   
   >> Às 04:14 de 09-07-2018, Carlos E.R. escreveu:   
   >>> On 2018-07-09 04:20, Paulo da Silva wrote:   
   >>>> Às 19:39 de 08-07-2018, Carlos E.R. escreveu:   
   >>>>> On 2018-07-08 16:19, Paul Thompson wrote:   
   >>>>>> On 07/07/2018 01:53 PM, Carlos E.R. wrote:   
   >>>>>   
   >>>> ...   
   ...   
      
   >   
   > Well, the interesting concoction would be a command to find out if any   
   > of the subvolumes is full or some sort of trouble.   
   >   
   Both previous commands show the space used and free of the whole volume,   
   i.e. if a subvolume is specified the output is about the volume that   
   contains that subvolume.   
   This is true if, at least, "quotas" are not used. Unfortunately I don't   
   use quotas and don't know how that works.   
      
   Another useful commands, to look for errors, may be for example   
      
   btrfs dev stats /bar   
   or, a command that should be run periodically,   
   btrfs scrub start /bar   
   This last one is asynchronous and must be handled with   
   btrfs scrub status /bar   
   btrfs scrub cancel /bar (eventually)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)