16 Jun
2019
16 Jun
'19
3:05 p.m.
Greetings;
Over the last several days, kmail has gotten so unstable its not usable.
Now tdewallet has also died, I have submitted 20+ crash reports, no
reply, and I've no clue if it will even send this message. How about
some help or an acnowlegement of the problem. I've rebooted, even
re-installed all of kmail to no avail. I've also run memtest about 3 full
cycles, no errors.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
16 Jun
16 Jun
3:44 p.m.
New subject: [trinity-users] kmail crashing now unusable
Hi Gene!
Which system are you on?
Nik
Anno domini 2019 Sun, 16 Jun 11:05:43 -0400
Gene Heskett scripsit:
Greetings;
Over the last several days, kmail has gotten so unstable its not usable.
Now tdewallet has also died, I have submitted 20+ crash reports, no
reply, and I've no clue if it will even send this message. How about
some help or an acnowlegement of the problem. I've rebooted, even
re-installed all of kmail to no avail. I've also run memtest about 3 full
cycles, no errors.
Cheers, Gene Heskett
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
6:54 p.m.
New subject: [trinity-users] Re: kmail crashing now unusable
Anno domini 2019 Sun, 16 Jun 20:50:15 +0200
deloptes scripsit:
Dr. Nikolaus Klepp wrote:
I'm on a Frankenpad ;)
Hi Gene!
Which system are you on?
I bet he's on some kind of frankenstein :)
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
19 Jun
19 Jun
6:44 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Sunday 16 June 2019 11:05:43 am Gene Heskett wrote:
Greetings;
Over the last several days, kmail has gotten so unstable its not
usable. Now tdewallet has also died, I have submitted 20+ crash
reports, no reply, and I've no clue if it will even send this message.
How about some help or an acnowlegement of the problem. I've
rebooted, even re-installed all of kmail to no avail. I've also run
memtest about 3 full cycles, no errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to 4.9.0.9,
without the rt. Kmail always has a cow over to folders indices, so I
expected to get a message about spam and spam-hold which both get
touched by external scripts or by me moving messages around, but even if
a nuke all the index files and then start or restart kmail, it has the
rebuild done in 15 minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone berzackers:
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop it, and nuke
then all. Then restart and time it.
Back later with the results.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
6:49 p.m.
New subject: [trinity-users] kmail crashing now unusable
said Gene Heskett:
| I just changed kernels on this machine, from 4.9.0.9-rt to 4.9.0.9,
| without the rt. Kmail always has a cow over to folders indices, so I
| expected to get a message about spam and spam-hold which both get
| touched by external scripts or by me moving messages around, but even if
| a nuke all the index files and then start or restart kmail, it has the
| rebuild done in 15 minutes or so.
remind us whether you're using maildir (good) or mbox (bad). (which
appraisals i give based on the ability to recover messages in case of a
problem.)
--
dep
Some pictures:
http://www.ipernity.com/doc/depscribe/album
7:48 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Wednesday 19 June 2019 02:44:35 pm Gene Heskett wrote:
On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
Back to a stable kmail, but it crashed about 2 secs after the first
start. With zero indices it took 1:31 to start, but its still using a
whole core at 100%, and the wc -l is growing by 10 or 20 almost
everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and 18
subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug.
Greetings;
Over the last several days, kmail has gotten so unstable its not
usable. Now tdewallet has also died, I have submitted 20+ crash
reports, no reply, and I've no clue if it will even send this
message. How about some help or an acnowlegement of the problem.
I've rebooted, even re-installed all of kmail to no avail. I've also
run memtest about 3 full cycles, no errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to 4.9.0.9,
without the rt. Kmail always has a cow over to folders indices, so I
expected to get a message about spam and spam-hold which both get
touched by external scripts or by me moving messages around, but even
if a nuke all the index files and then start or restart kmail, it has
the rebuild done in 15 minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop it, and
nuke then all. Then restart and time it.
Back later with the results.
Cheers, Gene Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
8:23 p.m.
New subject: [trinity-users] kmail crashing now unusable
Anno domini 2019 Wed, 19 Jun 15:48:24 -0400
Gene Heskett scripsit:
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
On Wednesday 19 June 2019 02:44:35 pm Gene Heskett
wrote:
Now this might not be a solution for you, but attorny prints out every email he receives
and each he sends. then he build subdirectories of physical folders. Think he has 50
meters of them ...
Nik
On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
Back to a stable kmail, but it crashed about 2 secs after the first
start. With zero indices it took 1:31 to start, but its still using a
whole core at 100%, and the wc -l is growing by 10 or 20 almost
everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and 18
subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug. Greetings;
Over the last several days, kmail has gotten so unstable its not
usable. Now tdewallet has also died, I have submitted 20+ crash
reports, no reply, and I've no clue if it will even send this
message. How about some help or an acnowlegement of the problem.
I've rebooted, even re-installed all of kmail to no avail. I've also
run memtest about 3 full cycles, no errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to 4.9.0.9,
without the rt. Kmail always has a cow over to folders indices, so I
expected to get a message about spam and spam-hold which both get
touched by external scripts or by me moving messages around, but even
if a nuke all the index files and then start or restart kmail, it has
the rebuild done in 15 minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop it, and
nuke then all. Then restart and time it.
Back later with the results.
Cheers, Gene Heskett
Cheers, Gene Heskett
9:14 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Wednesday 19 June 2019 04:23:44 pm Dr. Nikolaus Klepp wrote:
Anno domini 2019 Wed, 19 Jun 15:48:24 -0400
Gene Heskett scripsit:
A sense of humor helps. Doesn't fix it, but the grin makes me feel
better. And now I'd better go get my lady her daily dose of crossword
puzzles, and a few cans of pork and beans. I thought I had some but
didn't, took the pantry apart looking though when she wanted a teeny
bowl for lunch. This girl has probably never tasted a good ribeye or
filly mignon in her life. School teachers eat fast & cheap. Hard
habits to break and I've been working on it for 30 years. Hopeless I
tell you, hopeless.
On Wednesday 19 June 2019 02:44:35 pm Gene
Heskett wrote:
Now this might not be a solution for you, but attorny prints out every
email he receives and each he sends. then he build subdirectories of
physical folders. Think he has 50 meters of them ...
Nik On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
Back to a stable kmail, but it crashed about 2 secs after the first
start. With zero indices it took 1:31 to start, but its still using
a whole core at 100%, and the wc -l is growing by 10 or 20 almost
everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and 18
subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug. Greetings;
Over the last several days, kmail has gotten so unstable its not
usable. Now tdewallet has also died, I have submitted 20+ crash
reports, no reply, and I've no clue if it will even send this
message. How about some help or an acnowlegement of the problem.
I've rebooted, even re-installed all of kmail to no avail. I've
also run memtest about 3 full cycles, no errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to
4.9.0.9, without the rt. Kmail always has a cow over to folders
indices, so I expected to get a message about spam and spam-hold
which both get touched by external scripts or by me moving
messages around, but even if a nuke all the index files and then
start or restart kmail, it has the rebuild done in 15 minutes or
so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop it,
and nuke then all. Then restart and time it.
> > Back later with the results.
> >
> > Cheers, Gene Heskett
>
> Cheers, Gene Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
9:05 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Wednesday 19 June 2019 03:48:24 pm Gene Heskett wrote:
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Wednesday 19 June 2019 02:44:35 pm Gene Heskett
wrote:
Interesting hour, during which I got to exercise amanda's amrecover. I'd
committed Nik's fix message to a script, with a typu, and wiped the
whole MaryAnn, so I had to run amrecover, and recover the whole thing as
it existed about 2ish this morning. So I could be missing about 100
msgs that have come in since, or are we? The message I am replying to
was sent about an hour ago? Ghosts? DamnedifIknw.
Anyway the indices were nuked, kmail has renewed them, albeit w/o any
added marks. AND kmail has quit burning up a core in this old phenom.
Now, I had to change the ownership of two dir trees in /tmp before root
could run amrecover. So since amanda runs as amanda, I'd better check
that out. And amcheck seems to think its kewl.
But whats wrong with kmail? Why do I have to nuke ALL the index files to
make it happy again.
On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
Back to a stable kmail, but it crashed about 2 secs after the first
start. With zero indices it took 1:31 to start, but its still using a
whole core at 100%, and the wc -l is growing by 10 or 20 almost
everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and 18
subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug.
> Back later with the results.
> Greetings;
Over the last several days, kmail has gotten so unstable its not
usable. Now tdewallet has also died, I have submitted 20+ crash
reports, no reply, and I've no clue if it will even send this
message. How about some help or an acnowlegement of the problem.
I've rebooted, even re-installed all of kmail to no avail. I've
also run memtest about 3 full cycles, no errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to 4.9.0.9,
without the rt. Kmail always has a cow over to folders indices, so
I expected to get a message about spam and spam-hold which both get
touched by external scripts or by me moving messages around, but
even if a nuke all the index files and then start or restart kmail,
it has the rebuild done in 15 minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop it, and
nuke then all. Then restart and time it. Cheers, Gene
Heskett
Cheers, Gene Heskett 
20 Jun
20 Jun
6:44 a.m.
New subject: [trinity-users] kmail crashing now unusable
Hi Gene,
On Wednesday 19 June 2019 22:05:28 Gene Heskett wrote:
On Wednesday 19 June 2019 03:48:24 pm Gene Heskett
wrote:
Cheers, Gene Heskett
The more I read your posts, the more I'm concluding that you have a
hardware issue ! I would take a good look at the main board,
particularly around the CPU for bad capacitors. Also around the
memory sticks, though there may not be any signs of bad caps around
them.
Any that are leaking or even sightly swollen can be considered
faulty ! The other possible issue could be the main PSU itself.
Again bad capacitors in there will allow ripple and noise onto the
power rails to cause corruption. Non of these is easy to fix ! Some
will replace the bad components, but usually will just replace the
PSU and main board.
--
Best Regards:
Baron
On Wednesday 19 June 2019 02:44:35 pm Gene
Heskett wrote:
Interesting hour, during which I got to exercise amanda's
amrecover. I'd committed Nik's fix message to a script, with a
typu, and wiped the whole MaryAnn, so I had to run amrecover, and
recover the whole thing as it existed about 2ish this morning. So
I could be missing about 100 msgs that have come in since, or are
we? The message I am replying to was sent about an hour ago?
Ghosts? DamnedifIknw.
Anyway the indices were nuked, kmail has renewed them, albeit w/o
any added marks. AND kmail has quit burning up a core in this old
phenom.
Now, I had to change the ownership of two dir trees in /tmp before
root could run amrecover. So since amanda runs as amanda, I'd
better check that out. And amcheck seems to think its kewl.
But whats wrong with kmail? Why do I have to nuke ALL the index
files to make it happy again.
On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
Back to a stable kmail, but it crashed about 2 secs after the
first start. With zero indices it took 1:31 to start, but its
still using a whole core at 100%, and the wc -l is growing by 10
or 20 almost everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and
18 subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug.
> Back later with the results. Greetings;
Over the last several days, kmail has gotten so unstable its
not usable. Now tdewallet has also died, I have submitted 20+
crash reports, no reply, and I've no clue if it will even
send this message. How about some help or an acnowlegement of
the problem. I've rebooted, even re-installed all of kmail to
no avail. I've also run memtest about 3 full cycles, no
errors.
Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to
4.9.0.9, without the rt. Kmail always has a cow over to
folders indices, so I expected to get a message about spam and
spam-hold which both get touched by external scripts or by me
moving messages around, but even if a nuke all the index files
and then start or restart kmail, it has the rebuild done in 15
minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop
it, and nuke then all. Then restart and time it. Cheers,
Gene Heskett
Cheers, Gene Heskett
6:48 a.m.
New subject: [trinity-users] kmail crashing now unusable
Anno domini 2019 Thu, 20 Jun 07:44:15 +0100
Baron scripsit:
Hi Gene,
On Wednesday 19 June 2019 22:05:28 Gene Heskett wrote:
+1
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
On Wednesday 19 June 2019 03:48:24 pm Gene
Heskett wrote:
Cheers, Gene Heskett
The more I read your posts, the more I'm concluding that you have a
hardware issue ! I would take a good look at the main board,
particularly around the CPU for bad capacitors. Also around the
memory sticks, though there may not be any signs of bad caps around
them.
Any that are leaking or even sightly swollen can be considered
faulty ! The other possible issue could be the main PSU itself.
Again bad capacitors in there will allow ripple and noise onto the
power rails to cause corruption. Non of these is easy to fix ! Some
will replace the bad components, but usually will just replace the
PSU and main board.
On Wednesday 19 June 2019 02:44:35 pm Gene
Heskett wrote:
Interesting hour, during which I got to exercise amanda's
amrecover. I'd committed Nik's fix message to a script, with a
typu, and wiped the whole MaryAnn, so I had to run amrecover, and
recover the whole thing as it existed about 2ish this morning. So
I could be missing about 100 msgs that have come in since, or are
we? The message I am replying to was sent about an hour ago?
Ghosts? DamnedifIknw.
Anyway the indices were nuked, kmail has renewed them, albeit w/o
any added marks. AND kmail has quit burning up a core in this old
phenom.
Now, I had to change the ownership of two dir trees in /tmp before
root could run amrecover. So since amanda runs as amanda, I'd
better check that out. And amcheck seems to think its kewl.
But whats wrong with kmail? Why do I have to nuke ALL the index
files to make it happy again.
On Sunday 16 June 2019 11:05:43 am Gene Heskett
wrote:
> Greetings;
>
> Over the last several days, kmail has gotten so unstable its
> not usable. Now tdewallet has also died, I have submitted 20+
> crash reports, no reply, and I've no clue if it will even
> send this message. How about some help or an acnowlegement of
> the problem. I've rebooted, even re-installed all of kmail to
> no avail. I've also run memtest about 3 full cycles, no
> errors.
>
>
> Cheers, Gene Heskett
Let me add a bit more info to this kmail thread.
I just changed kernels on this machine, from 4.9.0.9-rt to
4.9.0.9, without the rt. Kmail always has a cow over to
folders indices, so I expected to get a message about spam and
spam-hold which both get touched by external scripts or by me
moving messages around, but even if a nuke all the index files
and then start or restart kmail, it has the rebuild done in 15
minutes or so.
But not this time. And lsof |grep index|wc -l shows its gone
berzackers: gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep Mail|wc -l
310
gene@coyote:~/PublicA$ lsof |grep index|wc -l
520
gene@coyote:~/PublicA$ lsof |grep index|wc -l
638
And it just keeps growing the number. So I'm going to stop
it, and nuke then all. Then restart and time it.
Back to a stable kmail, but it crashed about 2 secs after the
first start. With zero indices it took 1:31 to start, but its
still using a whole core at 100%, and the wc -l is growing by 10
or 20 almost everytime I rerun the lsof to get a new count
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
220
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
240
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
260
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
270
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
280
And theres only about 41 directorys, but 2 of those have 16 and
18 subdirs so theres not quite 80 dirs all told.
but there are 70147 msgs if I did it right, looks low.
gene@coyote:~$ lsof |grep Mail|grep .index|wc -l
380
Ladies and Gentlemen, I think we have a bug.
> Back later with the results. Cheers,
Gene Heskett
Cheers, Gene Heskett 
3:37 p.m.
New subject: [trinity-users] kmail crashing now unusable
Hi Gene,
But whats wrong with kmail? Why do I have to nuke ALL the index
files to make it happy again.
Only a farfetched thought.
Aren't you running out of memory plus swapspace when you fiddle around
with kmail?
What about the amount of free inodes on the concerned drive?
Regards.
4:46 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Thursday 20 June 2019 11:37:33 phiebie(a)drei.at wrote:
Hi Gene,
Its a 2T drive. df says
/dev/sda5 1857400436 221733604 1541246304 13% /
So I think that argument is close to null/void.
But whats wrong with kmail? Why do I have to
nuke ALL the index
files to make it happy again.
Only a farfetched thought.
Aren't you running out of memory plus swapspace when you fiddle around
with kmail?
What about the amount of free inodes on the concerned drive?
Regards.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
4:54 p.m.
New subject: [trinity-users] kmail crashing now unusable
df -i will show how many inodes there are plus used vs free
In theory an ext4 file-system can store 4 billion files regardless of
whether the disk is full or not. Not to say that is impossible but highly
unlikely you are at the limit.
If you are not using ext4 the number changes but still not a likely
scenario.
5:11 p.m.
New subject: [trinity-users] kmail crashing now unusable
On Thursday 20 June 2019 12:54:40 Pisini, John wrote:
df -i will show how many inodes there are plus used vs
free
In theory an ext4 file-system can store 4 billion files regardless of
whether the disk is full or not. Not to say that is impossible but
highly unlikely you are at the limit.
If you are not using ext4 the number changes but still not a likely
scenario.
/dev/sda5 118005760 1299904 116705856 2% /
I knew there was a limit, but 4 Billion? Boggle.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
5:14 p.m.
New subject: [trinity-users] Re: kmail crashing now unusable
On Thursday 20 June 2019 13:01:15 deloptes wrote:
Gene Heskett wrote:
Chuckle, close enough for the girls I go with.
try df -i & get
/dev/sda5 118005760 1299904 116705856 2% /
I'd have to say thats a never mind.
Its a 2T drive. df says
/dev/sda5 1857400436 221733604 1541246304 13% /
So I think that argument is close to null/void.
Gene,
it's not an answer try again
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
1782
days inactive
1786
days old
17 comments
7 participants
participants (7)
-
Baron -
deloptes -
dep -
Dr. Nikolaus Klepp -
Gene Heskett -
phiebie＠drei.at -
Pisini, John