xosview

xosview

[Klaus Dittrich]

Since 2.4.18p8 xosview does not work anymore.

Re: xosview

[J Sloan]

hmm -

It's working fine here on my 2 systems running
2.4.19-pre9aa2  and RH 7.3 kernel (2.4.18-4) -

Joe


Klaus Dittrich wrote:

>Since 2.4.18p8 xosview does not work anymore.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>

Re: xosview

[kwijibo]

I believe it is xosview that needs to change and not
the kernel.  Mine worked with pre8 however, my move
to pre10 broke it.

Steve

Klaus Dittrich wrote:

>Since 2.4.18p8 xosview does not work anymore.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>

Re: xosview

[Andrew Morton]

kwijibo@zianet.com wrote:
> 
> I believe it is xosview that needs to change and not
> the kernel.  Mine worked with pre8 however, my move
> to pre10 broke it.
> 

It's the gunk in /proc/stat which broke it.  Some
accidentally-included debug stuff.

--- linux-2.4.19-pre9/fs/proc/proc_misc.c	Tue May 28 17:23:37 2002
+++ linux-mnm/fs/proc/proc_misc.c	Tue Jun  4 23:25:12 2002
@@ -322,7 +322,7 @@ static int kstat_read_proc(char *page, c
 #if !defined(CONFIG_ARCH_S390)
 	for (i = 0 ; i < NR_IRQS ; i++)
 		proc_sprintf(page, &off, &len,
-			     " %u", kstat_irqs(i) + 1000000000);
+			     " %u", kstat_irqs(i));
 #endif
 
 	proc_sprintf(page, &off, &len, "\ndisk_io: ");

-

Re: xosview

[Kristian Peters]

kladit@t-online.de (Klaus Dittrich) wrote:
> Since 2.4.18p8 xosview does not work anymore.

That's a known problem. xosview tries to access /proc/stat that has a wierd format and a buffer goes beyond 1024 in xosview. I was also effected on this problem. It's been fixed in the next version of 2.4.19 (probably -rc1). In the meantime you can apply this patch:

diff -ur linux-2.4.19-pre9.org/fs/proc/proc_misc.c linux-2.4.19-pre9/fs/proc/proc_misc.c
--- linux-2.4.19-pre9.org/fs/proc/proc_misc.c	Wed May 29 01:26:17 2002
+++ linux-2.4.19-pre9/fs/proc/proc_misc.c	Thu May 30 03:09:07 2002
@@ -322,7 +322,7 @@
 #if !defined(CONFIG_ARCH_S390)
 	for (i = 0 ; i < NR_IRQS ; i++)
 		proc_sprintf(page, &off, &len,
-			     " %u", kstat_irqs(i) + 1000000000);
+			     " %u", kstat_irqs(i));
 #endif
 
 	proc_sprintf(page, &off, &len, "\ndisk_io: ");


*Kristian

  :... [snd.science] ...:
 ::                             _o)
 :: http://www.korseby.net      /\\
 :: http://gsmp.sf.net         _\_V
  :.........................:

Re: xosview

[Jochen Krieb]

Works fine here.

(2.4.18 & 2.4.19-pre10)

On Wed, 5 Jun 2002 08:07:02 +0200
kladit@t-online.de (Klaus Dittrich) wrote:

> Since 2.4.18p8 xosview does not work anymore.

xosview

[Klaus Dittrich]

I applied the patch from Andrew and xosview (1.8) works now.

xosview

[Anthony Youngman]

I don't know how many of you use this ancient nifty utility, but I've 
been using it for as long as I can remember. Unfortunately, the raid 
monitor code no longer works ... :-(

I emailed the maintainer privately and he was pleased that I'd got in 
touch even though it was with the bad news, and he'd like to fix it, but 
he has no system with raid to test it on.

It works by parsing /proc/mdstat. From what I can see of the code, it 
would be very easy to test it by pointing it at a fake mdstat. I've got 
three arrays on a two disk mirror, so that's easy for me to test, but 
I'd like to test it on other setups.

So if people wouldn't mind, could you email your mdstat files? 
Preferably on the list so people can see what has and has not been sent 
- obviously I'd like standard setups like raid10, raid5, raid6, both 
named and numbered. And if people have them, mdstats showing broken 
arrays, rebuilds, complicated setups with lvm, etc.

Dunno about other people, but I have xosview running on my desktop all 
the time (I feel naked without it :-) so if that can give me a 
continuous monitor of my raid state that's great. And hopefully, if 
other people use it, we might reduce the number of "I didn't realise my 
raid was degraded, and then it suffered another failure" type emails.

Cheers,
Wol

Re: xosview

[Glenn Enright]

On 30 July 2016 at 04:52, Anthony Youngman <antlists@youngman.org.uk> wrote:
>
> I don't know how many of you use this ancient nifty utility, but I've been using it for as long as I can remember. Unfortunately, the raid monitor code no longer works ... :-(
>
> I emailed the maintainer privately and he was pleased that I'd got in touch even though it was with the bad news, and he'd like to fix it, but he has no system with raid to test it on.
>
> It works by parsing /proc/mdstat. From what I can see of the code, it would be very easy to test it by pointing it at a fake mdstat. I've got three arrays on a two disk mirror, so that's easy for me to test, but I'd like to test it on other setups.
>
> So if people wouldn't mind, could you email your mdstat files? Preferably on the list so people can see what has and has not been sent - obviously I'd like standard setups like raid10, raid5, raid6, both named and numbered. And if people have them, mdstats showing broken arrays, rebuilds, complicated setups with lvm, etc.
>
> Dunno about other people, but I have xosview running on my desktop all the time (I feel naked without it :-) so if that can give me a continuous monitor of my raid state that's great. And hopefully, if other people use it, we might reduce the number of "I didn't realise my raid was degraded, and then it suffered another failure" type emails.
>
> Cheers,
> Wol
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


There are a number of good examples on
https://raid.wiki.kernel.org/index.php/Mdstat

This is from my desktop... (boot root and swap)

$ cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5]
[raid4] [raid10]
md1 : active raid1 sdb2[1] sda2[0]
      4194240 blocks [2/2] [UU]

md2 : active raid1 sdb3[1] sda3[0]
      62914496 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
      204736 blocks [2/2] [UU]

unused devices: <none>

Best
--Glenn

Re: xosview

[Bill Hudacek]

Anthony Youngman wrote on 07/29/2016 12:52 PM:
> So if people wouldn't mind, could you email your mdstat files?
> Preferably on the list so people can see what has and has not been sent
> - obviously I'd like standard setups like raid10, raid5, raid6, both
> named and numbered. And if people have them, mdstats showing broken
> arrays, rebuilds, complicated setups with lvm, etc.
>

RAID 6 across 5 disks, of which 1 is a spare (in external cabinet), 
and two disks in RAID-1 (for OS, inside the tower):

 > cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md0 : active raid6 sdc1[0] sdf1[3] sdd1[1] sdg1[4](S) sde1[2]
       3071737856 blocks super 1.2 level 6, 1024k chunk, algorithm 2 
[4/4] [UUUU]
       bitmap: 0/12 pages [0KB], 65536KB chunk

md126 : active raid1 sdb1[1] sda1[0]
       2099136 blocks super 1.0 [2/2] [UU]
       bitmap: 0/1 pages [0KB], 65536KB chunk

md127 : active raid1 sdb2[1] sda2[0]
       234921984 blocks super 1.2 [2/2] [UU]
       bitmap: 1/2 pages [4KB], 65536KB chunk

unused devices: <none>

I don't have any failure mdstat output saved, sorry...

-- 
/Bill

Re: xosview

[Wols Lists]

Thanks very much to all who replied :-)

The author is planning to rewrite based on /sys, however, so mdstat's
are likely no longer required ... the original raid code was donated,
and seems to have bit-rotted :-(

What I've said I'd like to see is the raid name and status - healthy,
rebuilding or degraded on the left; with the constituent
drives/partitions listed on the right, over colour bars indicating their
status (live, rebuilding, failed or spare). The author would also like
to add a status bar indicating the status of any rebuild.

So a healthy raid would be indicated by (default colours) green and
maybe blue for spare drives, while a degraded array would have red
around, and a rebuilding array would have yellow.

Anybody have any other ideas?

I know I'm bad at checking my raid status, and a lot of people probably
let the default install set up raid on a desktop without configuring
notification etc. It's just lovely to have a little utility like xosview
that can sit in the background on your desktop keeping an eye on things.
And that shows up instantly when things start going wrong. It keeps an
eye on my cpus, memory, swap space, and i/o. It could probably keep an
eye on more ...

Cheers,
Wol

On 01/08/16 19:50, Bill Hudacek wrote:
> Anthony Youngman wrote on 07/29/2016 12:52 PM:
>> So if people wouldn't mind, could you email your mdstat files?
>> Preferably on the list so people can see what has and has not been sent
>> - obviously I'd like standard setups like raid10, raid5, raid6, both
>> named and numbered. And if people have them, mdstats showing broken
>> arrays, rebuilds, complicated setups with lvm, etc.
>>
> 
> RAID 6 across 5 disks, of which 1 is a spare (in external cabinet), and
> two disks in RAID-1 (for OS, inside the tower):
> 
>> cat /proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4]
> md0 : active raid6 sdc1[0] sdf1[3] sdd1[1] sdg1[4](S) sde1[2]
>       3071737856 blocks super 1.2 level 6, 1024k chunk, algorithm 2
> [4/4] [UUUU]
>       bitmap: 0/12 pages [0KB], 65536KB chunk
> 
> md126 : active raid1 sdb1[1] sda1[0]
>       2099136 blocks super 1.0 [2/2] [UU]
>       bitmap: 0/1 pages [0KB], 65536KB chunk
> 
> md127 : active raid1 sdb2[1] sda2[0]
>       234921984 blocks super 1.2 [2/2] [UU]
>       bitmap: 1/2 pages [4KB], 65536KB chunk
> 
> unused devices: <none>
> 
> I don't have any failure mdstat output saved, sorry...
>