l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
October 7: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2003 Sep 10 10:41

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
RE: [vox-tech] File Access Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [vox-tech] File Access Question



Thanks

Also, if they are gone, is there a way to at least fix the problem of Linux
'thinking' the files are still there? i.e. even if the data is gone, I can't
write a file of the same name in that directory



> -----Original Message-----
> From: vox-tech-admin@lists.lugod.org
> [mailto:vox-tech-admin@lists.lugod.org]On Behalf Of Henry House
> Sent: Tuesday, September 09, 2003 12:38 PM
> To: vox-tech@lists.lugod.org
> Subject: Re: [vox-tech] File Access Question
>
>
> On Tue, Sep 09, 2003 at 12:29:54PM -0700, Andy Campbell wrote:
> [...]
> > Anyway, after the filesystem check, I go to the directory where I was
> > working and some files are not accessible. I get Input/Output
> errors when I
> > ls the files or when I try to access them at all. But evidently they are
> > still there.
> >
> > I come to your help now because one file is my source code, and it would
> > really be delightful if I could get it back. I really do not
> want to lose
> > the significant development I have done since my last file
> backup. I figured
> > someone on this list who knows more about the Linux filesystem
> than I do may
> > know what's going on and how I may get my precious file back.
> >
> > Any advice?
> > I am running RT-Linux 3.1 which has patched a 2.4.4 kernel,
> operating under
> > mandrake 8.1...
>
> Look in /lost+found. There is a chance that the data may be
> there. Otherwise,
> you are out of luck; the file was not written to disk and so went
> away with
> the power cycle.
>
> I recommend that you compile your kernel with the magic sysrq key enabled.
> (Sysrq is the same as printscreen.) This provides a some
> keystrokes that can
> usually sync the disk and reboot even if the kernel is otherwise
> unresponsive. See Documentation/sysrq.txt in the Linux kernel
> source tree for
> the details.
>
> You might also consider a journaling filesystem, such as ext3.
>
> --
> Henry House
> The unintelligible text that may follow is a digital signature.
> See <http://hajhouse.org/pgp> for information.  My OpenPGP key:
> <http://hajhouse.org/hajhouse.asc>.
>
>

_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!