similar to: Re:Re: fsck error

Hi all I have some problems with my config file. I used the guide from winehq to configure it. Here is the error message I get. [root@snort-par-office .wine]# wine -v Line 27: Unrecognized input 'Path=/usr/local/lib/win' Line 28: Unrecognized input 'Type=hd ' Line 29: Unrecognized input 'Label=Windows' Line 30: Unrecognized input 'Filesystem=win95' Line 33:

Hi all I was trying to isntall RApache last week but ran into strnge problems that no one else seems to be experiencing. At least I couldn't find anything after extensive googling. First off, the machine I'm installing on looks like this: Dell Optiplex 745 32 bit 2GB RAM Fedora 15 httpd -v Server version: Apache/2.2.21 (Unix) Server built: Sep 13 2011 13:46:23 R: R-2.14.0-3.fc15.i686

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from

Hi, this site: http://www.uow.edu.au/~andrewm/linux/ext3/ says "Forbidden" when I try to access .... , where can I download the ext3 patch for 2.4.15 ? Thank you Nikolai

On 23 July 2018 at 11:00, <r-sig-debian-request at r-project.org> wrote: Message: 1 > Date: Mon, 23 Jul 2018 02:08:47 +0000 > From: Alison Smith <alismith at uow.edu.au> > To: "r-sig-debian at r-project.org" <r-sig-debian at r-project.org> > Subject: [R-sig-Debian] Ubuntu issue with 18.04 Bionic Beaver > Message-ID: <1532311727386.27944 at

Dear Debian persons I would like enquire about whether the repository deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ I tried to follow the instructions and I cannot get R3.5.1 - I get R3.4.4??? I have been able to install R3.5.1 on Ubuntu 16.02 using the xenial-cran35/ repository & so not sure if the bionic link is up to date? thanks in advance Regards Alison

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

drbd-0.7.19 under kernel 2.6.17-rc4 is running on a primary node standalone. There are 8 resources in the same group. fsck.ext3 -fv is being run simultaneously on all of them. Each of the drbd devices are running on an lv, which all belong to a single pv. The actual "disk" is a hardware RAID connected via SCSI (i.e., the mpt driver). Five of the fsck finished their tasks

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20051010/1f0b0bc2/attachment.htm>

hi, I am working on a file system related project. I want to know whether the fsck utility for ext3 reads data blocks (storing user files,etc) at any stage? thankin you, amol __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Recently our sysadm accidentally powercycled our server (RedHat8) after 198 days of uptime, and upon boot it insisted on checking one partition (/dev/sda7) in our RAID. When it was done, the files were in the state of August 23 last year, with anything newer either gone or invisible. I guess something went wrong with journaling data. What can I do to restore the current state (except restore from

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Hi, got a very severe problem. I have two hard drives in my RS server and I am getting the secondary drive removed. Here's the problem. After the secondary drive is removed, the server fails to bootup completely, crashing at fsck. The server boots up fine when the secondary drive is put back in however. Has anyone ever encountered this problem before? Could the problem be to references to

Hi, folks A black out corrupted my file system (ext3, RH7.1). When I boot, the following message shows up: hdb: Quantum Fireball CR4.3A, ATA Disk Drive EXT3-fs error (device ide0 (3,66)): ext3_get_inode_loc: group >= groups count EXT3-fs: invalid journal inode EXT2-fs error (devide ide0 (3,66)): ext2_read_inode: group >= groups count EXT2-fs: corrupt root inode, run e2fsck Kernel Panic:

Hi Ryan, >> This is a completely fresh loopback EXT3 filesystem, untouched by fsck -D, >> and normally unmounted. > Oh, and I've attached the current version of my test program if anyone is > interested. > ... > It can corrupt my loopback test filesystems in under 5 minutes. Note that it > will completely destroy any data in its working directory, however. I am

Hi Ryan, > I am running your program now over an hour without any corruption on the > loopback mounted ext3 filesystem. shit, I thought testing over an hour (10mins your program, umount, fsck -fD test.img in a loop) is enough but it isn't. Damn f*ck :( root@codeman:[/] # fsck -fD test.img fsck 1.29 (24-Sep-2002) e2fsck 1.29 (24-Sep-2002) Truncating orphaned inode 6871 (uid=0, gid=0,

Hey, i have compiled ext3 as a module in the kernel. Also my entry for my / partition in the fstab says ext3, but when there is a power failure and i reboot the fsck starts running? Also it starts doing its normal procedure, with the 'salvaging and other fixes' Why is it so? also when i do a 'lsmod' it does not show the ext3 in it. Even dmesg shows that my / is initially

Hi, can anyone give me an example of when an fsck would repair something that the ext3 driver would not? with full "data=journal" journaling, would fsck ever need to be run if all the partitions were ext3? the ext3 mini-howto refers to "certain rare hardware failure cases (e.g. hard drive failures)" that would require a filesystem check, but doesn't go into details.

Hi all, I seem to be having a problem whereby my ext3 filesystem forces a full fsck on every hard system crash. This takes over 20 minutes on my 40GB drive and is driving me nuts. I've verified that the partition is, in fact, being mounted as ext3 and have tried removing ^has_journal and re-creating the journal file but nothing has worked. I'm running RH7.2... Any ideas would be much

Hi all, I'm running ext3 with Linux 2.4.19pre5aa2 (and thus ext3 0.9.17) and e2fsprogs 1.27 on an x86 laptop with an IDE disk (with DMA enabled). The partition in question was mounted with the data=journal and nosuid options set. All the partitions are set to be fscked on bootup every 30 days (although I don't think this is strictely necessary, better safe than sorry). ext3 has been