similar to: Check journal is replayable ?

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

From: Mark Milhollan Sent: April 21, 2015 05:35 > On Mon, 20 Apr 2015, Hugh E Cruickshank wrote: > > >CentOS 6 > > >From ''man fstab'' ... > > The sixth field, (fs_passno), is used by the fsck(8) > program to determine the order > in which filesystem checks are done at reboot time. > The root filesystem should be >

From: Les Mikesell Sent: April 21, 2015 09:19 > > Why do you care about running them at the same time when it doesn't > take longer to run them all in parallel? Except I think the root > filesystem normally runs first. So you might want to stagger it vs. > everything else. I am trying to avoid running them at the same time in an effort to avoid 70 minute boot times (which is

Il 14/05/2015 13:40, Tris Hoar ha scritto: > On 14/05/2015 10:16, Alessandro Baggi wrote: >> Hi List, >> I've installed C7.1 and today configuring fstab for another disk I get >> this: >> >> UUID=d5ff30df-9e1d-4fc8-99b6-845ffa6509db / xfs >> defaults 0 0 >> UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data

Hi there, I'm running software raid 1 across two 60GB IDE drives and booting off the raid device. The raid device holds an ext3 filesystem. Each drive is configured as a master on its own bus. The system is redhat 7.2, stock kernel 2.4.9-31smp. The hardware platform is a Dell precision dual 2Ghz P4 system with 1G of memory. I have two of these systems, both configured identitically.

Hey! I have some RHEL6 hypervisors and the VMs are in raw qemu image files in a local raid array linux raid + lvm + ext3. When a kernel update is installed a reboot is necessary, usually it has been more than 180 days since the last reboot and the file system is fsck'd and this takes 2-3 hours. I am curious to know if there is any documentation that addresses the pro's and con's of

Hi, After our big ext3 file server crashes, I notice the fsck spends some time replaying the journals (about 5-10 mins for all volumes on the server in question). I guess it must do this should you want to mount the volumes as ext2. My question--is it (theoretically) possible to tell fsck only to replay half-finished and to knock out incomplete transactions from the journals, leaving the kernel

CentOS 6 Hi All: Over the weekend I had to reboot one of my systems and got hit with fsck runs on all of the filesystems. I would not mind so much except doing them all at once took over an hour. I would like to be able to stagger these, ideally only execute one fsck per reboot. I have been able to think of two possible solutions but neither is terrific. My first idea was to manually run fsck

Hi List, I've installed C7.1 and today configuring fstab for another disk I get this: UUID=d5ff30df-9e1d-4fc8-99b6-845ffa6509db / xfs defaults 0 0 UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs defaults 0 0 UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap defaults 0 0 Fields fs_freq and fs_passno

From: Kay Diederichs Sent: April 21, 2015 03:43 > On 04/21/2015 06:08 AM, Hugh E Cruickshank wrote: > > > > The second idea was to set each filesystem to a different random > > count value. This would run the risk of having two or more > > executions at the same time but it would probably not be very > > frequent. > > Using "tune2fs -c", set the

From: Warren Young Sent: April 21, 2015 14:13 > On Apr 21, 2015, at 9:50 AM, Hugh E Cruickshank wrote: > > > > From: Kay Diederichs Sent: April 21, 2015 03:43 > >> > >> instead of having 20 for all of them, set > >> the first filesystem to 17, the second to 19, the third to > 23, and the > >> fourth to 29. > > > > Thanks but

Im brand new to rsync and i been doing alot of reading about it and it looks like the tool I have long been wanting. Bascially i got 1 server, 2 hard drives. partions are / /boot /home /usr /var /backup (2nd drive) Bascially what i am looking at doing is mirroring the first drive to the 2nd drive, and once that intial one is moved over, have a cron run nightly (or when specified) that will

Hello, Yesterday evening this box crashed and, for once, ext3 was not able to recover automatically. There was an "unexpected inconsistency inode xxxxx has imagic flag set" error and the system would not boot. I fscked from my rescue disk and I guess 20 or 30 errors were fixed by me just selecting "y" at the prompt. The system then booted and, so far as I can tell, the only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

From: Gordon Messmer Sent: April 21, 2015 10:30 > > On 04/21/2015 09:40 AM, Hugh E Cruickshank wrote: > > I accept that fscks are required on a periodic basis and I > am willing > > to reboot more often to achieve these but I would like to minimize > > downtime (during the reboot) where possible. > > Why do you accept that? Every article I have read on the

Hi, I run several hundred servers that are used heavily (webhosting, etc.) all day long. Quite often we'll have a server that either needs a really long fsck (10 hours - 200 gig drive) or an fsck that evntually results in everything going to lost+found (pretty much a total loss). Would rebooting these servers monthly (or some other frequency) stop this? Is it correct to visualize this as

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem

Every 24 mounts, fsck runs. Often enough, this run will fail demanding a manual run. This -f manual runs goes through its stages and only on rare occasion finds an orphaned node. 99%, finds noting amiss. Any reason for these "failures"?

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are

Hi, Can someone help explain why sometimes ext3 failed to recover from a sudden loss of power (ie. has to run lengthy fsck on paritions)? This happened to Redhat 7.2, 7.3 with latest stable kernel. Simon Gao