Re: Orphaned Inode Problem

2024-02-22 Thread Jörg-Volker Peetz
Henning Follmann wrote on 22/02/2024 08:43: You didn't answer where you read that. I would be interested in that. I do not claim to be an expert on this and I would like to understand it better. -H Concededly, I didn't noted that down. It was a discussion like in this blog:

Re: Orphaned Inode Problem

2024-02-21 Thread Henning Follmann
On Wed, Feb 21, 2024 at 05:15:55PM +0100, Jörg-Volker Peetz wrote: > Henning Follmann wrote on 21/02/2024 14:16: > > On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote: > > > > Somewhere I read, for maintainance of an SSD all it's cells should be read > > > from time to time like

Re: Orphaned Inode Problem

2024-02-21 Thread tomas
On Wed, Feb 21, 2024 at 05:15:55PM +0100, Jörg-Volker Peetz wrote: > Henning Follmann wrote on 21/02/2024 14:16: > > On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote: > > > > Somewhere I read, for maintainance of an SSD all it's cells should be read > > > from time to time like

Re: Orphaned Inode Problem

2024-02-21 Thread gene heskett
On 2/21/24 08:17, Henning Follmann wrote: On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote: Hi, did you take a look at the smartctl output? Somewhere I read, for maintainance of an SSD all it's cells should be read from time to time like this sudo dd if=/dev/DEVICE

Re: Orphaned Inode Problem

2024-02-21 Thread Gremlin
On 2/21/24 13:14, David Christensen wrote: On 2/21/24 03:00, Jörg-Volker Peetz wrote: Hi, did you take a look at the smartctl output? Somewhere I read, for maintainance of an SSD all it's cells should be read from time to time like this sudo dd if=/dev/DEVICE of=/dev/null bs=8M

Re: Orphaned Inode Problem

2024-02-21 Thread David Christensen
On 2/21/24 03:00, Jörg-Volker Peetz wrote: Hi, did you take a look at the smartctl output? Somewhere I read, for maintainance of an SSD all it's cells should be read from time to time like this sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress where device is something like sda or

Re: Orphaned Inode Problem

2024-02-21 Thread Jörg-Volker Peetz
Henning Follmann wrote on 21/02/2024 14:16: On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote: Somewhere I read, for maintainance of an SSD all it's cells should be read from time to time like this sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress Where did you read

Re: Orphaned Inode Problem

2024-02-21 Thread Henning Follmann
On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote: > Hi, > > did you take a look at the smartctl output? > > Somewhere I read, for maintainance of an SSD all it's cells should be read > from time to time like this > > sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress

Re: Orphaned Inode Problem

2024-02-21 Thread Jörg-Volker Peetz
Hi, did you take a look at the smartctl output? Somewhere I read, for maintainance of an SSD all it's cells should be read from time to time like this sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress where device is something like sda or nvme0n1, especially if it was switched off

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

2024-02-20 Thread Eike Lantzsch ZP5CGE / KY4PZ
On Dienstag, 20. Februar 2024 06:58:31 -03 Eike Lantzsch ZP5CGE / KY4PZ wrote: > On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote: > > Hi, > > > > On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / > > KY4PZ > wrote: > > > The notorious red SATA cables - I threw them out

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

2024-02-20 Thread Eike Lantzsch ZP5CGE / KY4PZ
On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote: > Hi, > > On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote: > > The notorious red SATA cables - I threw them out long ago. The red > > pigment eats up the fine copper threads, changing the impedance of > > the

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

2024-02-19 Thread jeremy ardley
On 20/2/24 08:48, Andy Smith wrote: Hi, On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote: The notorious red SATA cables - I threw them out long ago. The red pigment eats up the fine copper threads, changing the impedance of the cable and eventually making false

Re: red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

2024-02-19 Thread gene heskett
On 2/19/24 19:49, Andy Smith wrote: Hi, On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote: The notorious red SATA cables - I threw them out long ago. The red pigment eats up the fine copper threads, changing the impedance of the cable and eventually making false

red SATA cables "notoriously bad"? (Was Re: Orphaned Inode Problem)

2024-02-19 Thread Andy Smith
Hi, On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote: > The notorious red SATA cables - I threw them out long ago. The red > pigment eats up the fine copper threads, changing the impedance of the > cable and eventually making false contact before failing completely.

Re: Orphaned Inode Problem

2024-02-19 Thread Eike Lantzsch ZP5CGE / KY4PZ
On Montag, 19. Februar 2024 14:20:52 -03 to...@tuxteam.de wrote: > On Mon, Feb 19, 2024 at 10:02:10AM -0500, Stephen P. Molnar wrote: > > I am running up to date Bookworm on my Debian platform: > > > > Processor AMD FX(tm)-8320 Eight-Core Processor > > Memory 8026MB (5267MB used) > >

Re: Orphaned Inode Problem

2024-02-19 Thread tomas
On Mon, Feb 19, 2024 at 12:30:30PM -0500, Stephen P. Molnar wrote: [...] > Thanks for he reply. It's somewhat reassuring. > > According to my logs the box had its' last major  last upgrade in 2014, so I > shouldn't be too surprised. > > My backup is underweight and should be done sometime

Re: Orphaned Inode Problem

2024-02-19 Thread Stephen P. Molnar
On 02/19/2024 12:20 PM, to...@tuxteam.de wrote: On Mon, Feb 19, 2024 at 10:02:10AM -0500, Stephen P. Molnar wrote: I am running up to date Bookworm on my Debian platform: Processor AMD FX(tm)-8320 Eight-Core Processor Memory 8026MB (5267MB used) Machine TypeDesktop Operating

Re: Orphaned Inode Problem

2024-02-19 Thread tomas
On Mon, Feb 19, 2024 at 10:02:10AM -0500, Stephen P. Molnar wrote: > I am running up to date Bookworm on my Debian platform: > > Processor AMD FX(tm)-8320 Eight-Core Processor > Memory8026MB (5267MB used) > Machine Type Desktop > Operating System Debian GNU/Linux 12 (bookworm) >

Orphaned Inode Problem

2024-02-19 Thread Stephen P. Molnar
I am running up to date Bookworm on my Debian platform: Processor AMD FX(tm)-8320 Eight-Core Processor Memory 8026MB (5267MB used) Machine TypeDesktop Operating SystemDebian GNU/Linux 12 (bookworm) I have been plagued with orphaned inodes. Last night the problem cane to a

Re: Orphaned Inode Problem

2019-11-20 Thread Stephen P. Molnar
Well, as I said, I didn't know if it meant anything. On 11/20/2019 11:01 AM, Reco wrote: Hi. On Wed, Nov 20, 2019 at 09:19:30AM -0500, Stephen P. Molnar wrote: I don't know what the significance might be, but I have installed Buster in an Oracle VM along with the software that hangs,

Re: Orphaned Inode Problem

2019-11-20 Thread Reco
Hi. On Wed, Nov 20, 2019 at 09:19:30AM -0500, Stephen P. Molnar wrote: > I don't know what the significance might be, but I have installed > Buster in an Oracle VM along with the software that hangs, and it > works. Countless things could be significant here. If you remove a real

Re: Orphaned Inode Problem

2019-11-20 Thread Stephen P. Molnar
I don't know what the significance might be, but I have installed Buster in an Oracle VM along with the software that hangs, and it works. On 11/19/2019 02:39 PM, Reco wrote: Hi. On Tue, Nov 19, 2019 at 02:31:59PM -0500, Stephen P. Molnar wrote: On Mon, Nov 18, 2019 at 02:06:48PM

Re: Orphaned Inode Problem

2019-11-19 Thread Ben Caradoc-Davies
On 19/11/2019 08:17, Reco wrote: A kernel panic or OOPS comes to mind first. That's very broad class of the problem, to say the least, hence the need of kernel logs. Xorg hang is the second possible option. AMD hardware is somewhat problematic here. Barring above - an overheat is the third

Re: Orphaned Inode Problem

2019-11-19 Thread Reco
Hi. On Tue, Nov 19, 2019 at 02:31:59PM -0500, Stephen P. Molnar wrote: > > On Mon, Nov 18, 2019 at 02:06:48PM -0500, Stephen P. Molnar wrote: > > > he problem is that the program hangs and the system will not > > > recognized the keyboard, although, according to gKrellM the system is > >

Re: Orphaned Inode Problem

2019-11-19 Thread Stephen P. Molnar
On 11/18/2019 02:17 PM, Reco wrote: Hi. On Mon, Nov 18, 2019 at 02:06:48PM -0500, Stephen P. Molnar wrote: he problem is that the program hangs and the system will not recognized the keyboard, although, according to gKrellM the system is still operating. The only solution seems to be

Re: Orphaned Inode Problem

2019-11-18 Thread Pascal Hambourg
Le 18/11/2019 à 20:06, Stephen P. Molnar a écrit : The CPU is an AMD FX-8320 Eight-Core Processor on an ASUSTeK M5A97 R2.0 Motherboard with 8GB Ram. I have started having orphaned inodes when I run a major piece of software in my research program. How do you know you have orphaned inodes

Re: Orphaned Inode Problem

2019-11-18 Thread Dan Ritter
Reco wrote: > Hi. > > On Mon, Nov 18, 2019 at 02:06:48PM -0500, Stephen P. Molnar wrote: > > he problem is that the program hangs and the system will not > > recognized the keyboard, although, according to gKrellM the system is > > still operating. The only solution seems to be to reboot

Re: Orphaned Inode Problem

2019-11-18 Thread Reco
Hi. On Mon, Nov 18, 2019 at 02:06:48PM -0500, Stephen P. Molnar wrote: > he problem is that the program hangs and the system will not > recognized the keyboard, although, according to gKrellM the system is > still operating. The only solution seems to be to reboot the system. The

Orphaned Inode Problem

2019-11-18 Thread Stephen P. Molnar
I am running Stretch on my Linux platform. The CPU is an AMD FX-8320 Eight-Core Processor on an ASUSTeK M5A97 R2.0 Motherboard with 8GB Ram. I have started having orphaned inodes when I run a major piece of software in my research program. he problem is that the program hangs and the system