<br><br><div><span class="gmail_quote">On 7/16/06, <b class="gmail_sendername">Hans Reiser</b> <<a href="mailto:reiser@namesys.com">reiser@namesys.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ryan Steffes wrote:<br><br>><br>><br>> On 7/14/06, *Michael T. Dean* <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a><br>> <mailto:<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com
</a>>> wrote:<br>><br>> On 07/14/2006 09:31 PM, Carl Fongheiser wrote:<br>> > On 7/14/06, *Ryan Steffes* <<a href="mailto:rbsteffes@gmail.com">rbsteffes@gmail.com</a><br>> <mailto:<a href="mailto:rbsteffes@gmail.com">
rbsteffes@gmail.com</a>><br>> > <mailto:<a href="mailto:rbsteffes@gmail.com">rbsteffes@gmail.com</a> <mailto:<a href="mailto:rbsteffes@gmail.com">rbsteffes@gmail.com</a>>>> wrote:<br>> >
<br>> > I've never seen ls do this before, at least, not for root. Any<br>> > idea what could cause it?<br>> ><br>> > # ls<br>> > ls: 1036_20060417230000_20060417233000.nuv.png: Permission
<br>> denied<br>> > ls: 1056_20060610130000.mpg: Permission denied<br>> > ls: 1006_20050920213000_20050920220000.nuv.png: Permission<br>> denied<br>> > ls: 1013_20060420201900_20060420203000.nuv: Permission denied
<br>> > ls: 1003_20060419220000_20060419230000.nuv.png: Permission<br>> denied<br>> ><br>> > Can't delete em, look at em, touch em, chmod em, or chown<br>> em, even<br>> > as root. It's odd.
<br>> ><br>> ><br>> > Are these files on a remote NFS share? If so, that's not unusual.<br>> > Root is usually mapped to "nobody" on remote NFS servers.<br>><br>> Or, it could happen because of a stale NFS file handle (fixable by
<br>> unmounting/remounting).<br>><br>> Mike<br>> _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org
</a> <mailto:<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br>><br>><br>><br>> It appears the answer I may have to go with is some sort of corruption<br>> in the file system. I'm CCing this to the reiserfs list, since that's<br>> what the partition is. On reboot, the partition starts to load, and
<br>> hangs up on "Checking Internal Tree.." and gets no further.<br>><br>> Any suggestions on how to recover without losing all my data?<br>><br>> Ryan<br>><br>><br>Send lots more details to
<a href="mailto:vs@namesys.com">vs@namesys.com</a>.<br></blockquote></div><br><br>I believe I have the answer now, I'm not sure more details will do you good. The culprit appears to be a bad stick of RAM. The advice about checking RAM before rechecking the reiserfs tree is a very good one, I wish I had gotten it a couple days ago. Faulty RAM removed, I was about to rebuild-tree and lose nothing that I've noticed.
<br><br>Thanks for the help!<br><br>Ryan<br>