[reiserfs-list] Filesystem Corruption

2002-06-06 Thread Kurt

  
 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]> 
 to file:  06/06/2002 02:00 PM
 pic13835.pcx)
  







Hello all,
 I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj239G  142G   97G  60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt



--
====
Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846



[reiserfs-list] Filesystem Corruption

2002-06-06 Thread Kurt

  
 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]> 
 to file:  06/06/2002 02:00 PM
 pic24262.pcx)
  








 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic13835.pcx)








Hello all,
 I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj239G  142G   97G  60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt



--
====
Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846



[reiserfs-list] Filesystem Corruption

2002-06-06 Thread Kurt

  
 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]> 
 to file:  06/06/2002 02:00 PM
 pic11654.pcx)
  








 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic24262.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic13835.pcx)








Hello all,
 I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj239G  142G   97G  60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt



--
====
Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846



[reiserfs-list] Filesystem Corruption

2002-06-06 Thread Kurt

  
 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]> 
 to file:  06/06/2002 02:00 PM
 pic04883.pcx)
  








 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic11654.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic24262.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic13835.pcx)








Hello all,
 I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj239G  142G   97G  60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt



--
====
Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846



[reiserfs-list] Filesystem Corruption

2002-06-06 Thread Kurt

  
 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]> 
 to file:  06/06/2002 02:00 PM
 pic29967.pcx)
  








 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic30134.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic18956.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic19921.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic06540.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic08003.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic04883.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic11654.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic24262.pcx)









 (Embedded
 image moved   Kurt <[EMAIL PROTECTED]>
 to file:  06/06/2002 02:00 PM
 pic13835.pcx)








Hello all,
 I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj239G  142G   97G  60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt



--

Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846



Re: [reiserfs-list] Filesystem Corruption

2002-06-11 Thread Kurt

Thanks Oleg,
sorry for the late response (i was out of the office) , you may find 
the 
following information on the last crash useful :-
+++
3 04:32:37 devo kernel: vs-13075: reiserfs_read_inode2: dead inode read from 
disk [854 1695654 0x0 SD]. This is likely to be race with knfsd. Ignore
Jun  3 04:32:39 devo kernel: vs-13060: reiserfs_update_sd: stat data of object 
[854 1695654 0x0 SD] (nlink == 1) not found (pos 1)
Jun  3 04:41:38 devo kernel: vs-13060: reiserfs_update_sd: stat data of object 
[854 1695654 0x0 SD] (nlink == 1) not found (pos 1)
Jun  3 04:41:43 devo kernel: vs-13060: reiserfs_update_sd: stat data of object 
[854 1695654 0x0 SD] (nlink == 1) not found (pos 1)

I will upgrade the kernel and reiserfs tools this week and inform you of the 
result after a fsck.
-Kurt

On Friday 07 June 2002 3:15 am, Oleg Drokin wrote:
> Hello!
>
> On Thu, Jun 06, 2002 at 02:00:01PM -0400, Kurt wrote:
> > error stating the file pointed to nowhere.
> > I was unable to complete a reiserfsck --fix-fixable because of the length
> > of time that this (fsck) process took since this was an unscheduled
> > downtime. During the weekend i will attempt to do the fsck again, however
> > i really needed to know if this problem has been observed by anyone else,
> > and what steps they took to fix the problem.
>
> We recommend you to upgrade your kernel to 2.4.18.
> To know what exact problem is it would be very useful if you'd posted
> excerpts from kernel logs with actual errors.
> Thank you.
>
> Bye,
> Oleg

-- 

Kurt Palmer  SysAdmin
[EMAIL PROTECTED]Advance Internet
201-459-2846




reiserfs repairs

2004-09-29 Thread Kurt Guenther
I have some "wierd" files and I thought it may be from a long string of 
system crashes (due to nvidia/xorg-x11 issues).

enigma root # ls -ld .
drwx--  13 root root 776 Sep 27 16:45 .
enigma root # ls -ld ./README
ls: ./README: Permission denied
enigma root # ls -l ./README
ls: ./README: Permission denied
enigma root # ls -l
ls: README: Permission denied
ls: xorg.conf.new: Permission denied
total 533
-rw-r--r--  1 root root 541206 Sep 27 16:42 openvpn-2.0_beta11.tar.gz
enigma root #

It seems whatever existed in thid directory at the time of the crash has 
gone over to the dark side.  

I looked at reiserfsck, but it needs this file system to be be 
unmounted.  This is a remote RAID-1 server, so not much luck there.

What's the recommended approach to recover/delete these?   I'm running 
the 2.6.8-r3 Gentoo kernel.

--Kurt


RE: Problems with accessing directory

2005-05-29 Thread Kurt Ghekiere
Valdis,
Thank you for your info, 
Its Sunday evening in Belgium, we will have to find a solution
Because as ISP its that or cut the phone lines tomorrow :-)
If we find something we'll post it 
Thanks,
Kurt & Pascal 

-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Verzonden: zondag 29 mei 2005 20:05
Aan: Kurt Ghekiere
CC: Webservice; reiserfs-list@namesys.com
Onderwerp: Re: Problems with accessing directory 

On Sun, 29 May 2005 18:44:02 +0200, Kurt Ghekiere said:

> May 29 17:28:51 mail3 kernel: Process hax0r (pid: 3738,
> stackpage=f121b000)
> May 29 17:28:51 mail3 kernel: Stack:  bfe5 1000 
> f63b6000 bfffe7f0 f63b6000 b8e4 
> May 29 17:28:51 mail3 kernel:f78aaf22 0a3a 0020
f121a000
> c0108a93 000b bfffe7f0 f78a99a1
> May 29 17:28:51 mail3 kernel:  

>    
> May 29 17:28:51 mail3 kernel: Call Trace:[]
> May 29 17:28:51 mail3 kernel:
> May 29 17:28:51 mail3 kernel: Code: 8a 02 84 c0 75 ef e8 9c ec ff ff 
> 89
> c2 80 3a 00 0f 84 bb 00

Interesting process name indeed. Hopefully you recognize it? ;)

I would suggest running the call trace through ksymoops, but it's so
short that we've quite obviously clobbered the stack to the point that
ksymoops won't tell us anything useful.

I'd investigate why you get all those insmod errors - why is the system
trying to load pciehp and hw_random if there's no device?
Alternatively, are other modules getting loaded incorrectly and blocking
those from starting? It's possible that if your kernel and modules are
out of sync, that Bad Things like panics happen

You probably should look at upgrading the userspace reiserfsck and
MD/LVM tools
- your kernel seems unhappy with the old versions.

Other than that, I admit to not having any clear "AHA! THAT's their
problem"
solution, sorry