FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am running a Raid1 of four 100GB HD with LVM formated as EXT3. It worked qutie fine for a while and now everytime someone on the network writes to the fielsystem the whole thin is remounted read only and I get the following in my logfiles:
Apr 3 17:58:15 nlgsrv04 kernel: attempt to access beyond end of device
Apr 3 17:58:15 nlgsrv04 kernel: dm-0: rw=0, want=26551976680, limit=781418496
Apr 3 18:03:50 nlgsrv04 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 3 18:03:50 nlgsrv04 kernel: EXT3 FS on dm-0, internal journal
Apr 3 18:03:50 nlgsrv04 kernel: EXT3-fs: mounted filesystem with ordered data mode.
So I unmounted the LVM and let e2fsck check it... which gave me some of these:
Inode 2625555, i_Blocks ist 881576, sollte sein 881568. Repariere<j>? ja
Gelöscht Inode 27807865 hat "zero dtime". Repariere<j>? ja
In the end I run e2fsck a second time and the fs was reported clean... Remounted it, started samba and after the first write the same sh... again.