similar to: ext3 fsck question

Displaying 20 results from an estimated 6000 matches similar to: "ext3 fsck question"

2010 Oct 29
2
faster fsck ?
Hi, we have CentOS ftp server (vsftpd) which has a lot of users who are writing and reading a lot of small files from/into its own accounts (and other servers - using samba client - are reading these files and putting them into outside database). Since this server is under heavy load its availability is important. >From time to time we "crash" this server (don't ask why ...) but
2002 Oct 26
3
How come fsck still kicks in and reports major errors with Ext3?
Greetings. Total newbie with Ext3. I selected when I upgraded my system to RH7.2. I upgraded my system again to RH8.0. Here is some info: [root@world root]# cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 none /dev/shm tmpfs rw 0 0 none /dev/pts devpts rw 0 0 /dev/hdd1 /mnt/genericdata1 ext2 rw 0 0 Ok, so
2001 Jan 22
3
Possible funny with /sbin/fsck
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii Howdy - we have a bunch of dual processor Compaqs with 180GB RAID partitions for email, running with ext2 for the last year or so. I thought I'd try out ext3 (on our development machine :-) to see whether it was a practical proposition for this kind of thing yet. Appears to be working so far, with a
2009 Feb 05
1
Questions regarding journal replay
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
2007 Mar 21
1
Ext3 behavior on power failure
Hi all, We are building a new system which is going to use ext3 FS. We would like to know more about the behavior of ext3 in the case of failure. But before I procede, I would like to share more information about our future system. * Our application always does an fsync on files * When symbolic links (more specifically fast symlink) are created, the host directory is also fsync'ed. * Our
2017 May 15
1
Error messages in replayPlot()
I was wondering if there is something that can be done to improve error messages when replaying a recorded plot. For example a graphics device that is too small usually results in a helpful error message: png(height = 100) plot(1) # Error in plot.new() : figure margins too large dev.off() However when this happens when replaying a recorded plot, the error message is not so helpful. myplot
2004 Sep 24
1
openssh version
On Wed, 2 Jan 2002, John Hay wrote: > Well I can accept your argument for -stable, although bigger changes has > gone in -stable in the past, but what about -current? My -current boxes > also still claim: "sshd version OpenSSH_2.9 FreeBSD localisations > 20011202" And this is the problem, if we don't have -current upgraded > we have little chance in getting wrinkles
2001 Jul 11
4
Is this list active?
I subscribed this morning but have no traffic. Sometimes no traffic is a good thing. Since I've gone to ext3 on my 2.4.5 kernel, the only time I ever had problems was when the filesystems were not unmounted cleanly and the journal was lost. About 60 minutes of searching and reading and I found out how to recreate the journal. So far, so pleased with ext3fs. --
2019 Jun 26
10
[Bug 111007] New: Blender crash when opening material tab GTX 750Ti -- NV117 (GM107)
https://bugs.freedesktop.org/show_bug.cgi?id=111007 Bug ID: 111007 Summary: Blender crash when opening material tab GTX 750Ti -- NV117 (GM107) Product: Mesa Version: 19.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium
2002 Feb 17
1
root ext3 gets fsck'ed after crash
When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for
2020 Oct 05
3
what does "virsh destroy" really ?
Hi, what does "virsh destroy" with the domain ? Send a kill -9 to the process ? Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 HelmholtzZentrum München bernd.lentes@helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/mcd stay healthy
2006 Dec 18
1
Replay recorded plot with new layout
Folks, Please help with a graphics problem, I am running R2.4.0 on Windows XP. In much earlier version of R (1.3? about December 2001) I could par(mfrow=c(1,1)) plot(1,1,xlab="X",ylab="Y") plot1<-recordPlot() plot(2,2,xlab="X2",ylab="Y2") plot2<-recordPlot() par(mfrow=c(2,1)) plot1 plot2 and produce the same effect as the following
2008 Jul 14
4
FE driver and log dirty
Here''s a question about FE driver and log dirty, when live migration is concerned. Log dirty mode is used in live migration, which works for those polluted pages from CPU issued accesses, but not for DMA path (as BE driver talked here which access from another domain like dom0). Most frontend drivers don''t implement their own suspend interface (netfront implements when
2015 Jun 17
2
selinux allow apache log access
> > What turns up in myzabbix.te? Same deal. :( #semodule -i myzabbix.te semodule: Failed on myzabbix.te! sigh... but thanks any other clues? On Wed, Jun 17, 2015 at 11:42 AM, Harold Toms <h.toms at qmul.ac.uk> wrote: > On 17/06/15 16:29, Tim Dunphy wrote: > >> That's because there's already a zabbix module loaded (the message isn't >>> very
2006 Apr 17
2
Problem using plot and converted dates
Dear R-help, I am having problems with plotting converted dates in chronological as Mar-03, May-03...Jul-04. My script is: sam4<-c("03/03/01","03/05/01","03/07/01","03/09/01","03/11/01","04/01/01","04/03/01","04/05/01","04/07/01") sam5<-strptime(sam4,format="%y/%m/%d")
2010 Aug 31
4
e2fsck with millions of files
I have a large (1.5TB) partition with millions of files on it. e2fsck has been running nearly 12 hours and is still on "Checking directory structure". Any tips for speeding this along? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100831/8653d551/attachment-0002.html>
2014 May 01
2
Request to Replace Recordplot ,, replayplot
Record plot which stores a plot to an internal R data structure and Replay Plot which replays the plot enables one to keep plots around and use them accross sessions at least until version 3. If you cannot restore old plots and treat them as data and save accross sessions, there is little reason for recordPlot. Either R needs to dispense with internal formats entirelly, a bad move in my opinion
2002 Feb 20
2
ext3 + loop + journaling
[ If this is explained somewhere else (HOWTO or FAQ), please give me a pointer. ] Is there any way to mix loop-device (and in particular) loop-AES and ext3 together in data journaling mode? Ie. bottom -> to -> top ext3 - loop-AES - ext3 raw - loop-AES - ext3 Or am I shooting myself to leg, I am? BR, Jani -- Jani Averbach
2015 Jun 17
2
selinux allow apache log access
> > That's because there's already a zabbix module loaded (the message isn't > very informative!). I forgot that the received wisdom is to insert "my" in > front of ones own modules i.e.: > grep zabbix /var/log/audit/audit.log | audit2allow -M myzabbix > semodule -i myzabbix.pp Hmm no luck there either: [root at monitor2:~] #semodule -i myzabbix.pp
2009 May 20
1
[Fwd: Re: Unable to fix corrupt directories with fsck.ocfs2]
Robin, To me, anyone else includes the kernel of the current node. Well, if it is unclear the man page should be revised. Also a big warning message on ocfs2.fsck would be nice, after all we all make mistakes. But this is only my two cents. Running fsck on any journaled filesystem will replay the journal. This will cause corruption if the filesystem is mounted read/write, even if the