similar to: Backup questions - errors

Hi, although i'm using X11Forwarding only in my local environment, i'd like to avoid setting 'ForwardX11Trusted' to 'yes'. When starting applications like 'freerdp' on the remote machine while 'ForwardX11Trusted' is _not_ set to 'yes' on the client, the characters \ = 51 = <BKSL> backslash | = 94 = <LSGT> pipe won't work. Any

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

I've got a IBM BladeCenter with its integral TCPIP KVM and centos and stuff running on various blades, we use this mostly for software testing purposes in a small development group. i wanted to boot the liveCD so I could try and recover some files from a totally screwed up system (disk got fsck'd beyond what I feel comfortable repairing)... so I map an ISO image of the CentOS 4.4

I fsck'd it and it seems to be in pretty good shape. This is 2.4.18 - RH9. This machine can't handle file system problems. It has to stay RH9 but I could back out the journalling. The machine is only 3 months old. I don't think it's a hardware issue. No error messages and the symptom (aside from being unusable) was I/O error seeking <different blocks>. The fsck

Hi again all, I apologize for not asking this in my first message; I just remembered the question after sending. On Sun, Jun 01, 2014 at 07:43:12PM -0700, Keith Keller wrote: > > On Sun, Jun 01, 2014 at 09:05:09PM -0400, Theodore Ts'o wrote: > > Unfortunately, there has been a huge number of bug fixes for ext4's > > online resize since 2.6.32 and 1.42.11. It's

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.

On Nov 18, 2015, at 9:49 PM, Devin Reade <gdr at gno.org> wrote: > > The one thing I would point out regarding the above link is that despite > conventional UNIX wisdom, *don't* put /usr on a separate filesystem > in CentOS 7. <sarcasm>Thank you RedHat</sarcasm> > > Flames to /dev/null. Sorry, you don?t get to throw that grenade and then run away. The

Hi Bodo and Ted, Thank you both for your responses; they confirm what I thought might be the case. Knowing that I can try to proceed with your suggestions. I do have some followup questions for you: On Sun, Jun 01, 2014 at 09:05:09PM -0400, Theodore Ts'o wrote: > Unfortunately, there has been a huge number of bug fixes for ext4's > online resize since 2.6.32 and 1.42.11.

The 03/07/13, Jamie Fargen wrote: > 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

* Keith Keller <kkeller@wombat.san-francisco.ca.us> hat geschrieben: Hi Keith > I have a very similar second server which has undergone a similar chain > of events, an initial ~2.5tb fs followed by a resize later. I believe > that it has been fsck'd since the resize (but don't quote me on that). > Am I likely to run into this issue with this fs? And if I do, what >

--On Thursday, November 19, 2015 11:54:19 AM -0700 Warren Young <wyml at etr-usa.com> wrote: > ?Twas *progress* that made it so, specifically the fact > that even a throwaway USB key has enough space to hold the complete OS on > it these days. For the record, size of the disk was never the original motivation for keeping / separate, at least within my memory; it was to minimize

On Nov 19, 2015, at 3:49 PM, Devin Reade <gdr at gno.org> wrote: > > size of the disk was never the original motivation for > keeping / separate, at least within my memory Prior to SysV, the location of user home directories was not standardized, and AT&T recommended that you put them in /usr.[1] Also, in the PDP days, you had things like the RL and RK series drives, which

<expletive deleted> My roaming profiles keep "forgetting" they exist on my W2K boxen. It doesn't occur server-side, as other W2K clients log in fine. But, once one of the clients has forgotten about roaming profiles, it usually takes a re-install to make it remember them... and then, only temporarily. (Except on one machine that's worked fine from the get-go.) I even

Hello, I'm running the following script for backup: SHORTHOST=`hostname | awk 'BEGIN { FS="." } { print $1 }'` cd $HOME || exit 1 rsync --ignore-errors --max-size=50m -v --delete --delete-excluded --log-file=/tmp/backup.log --exclude-from=$HOME/.rsync/exclude \ --timeout=3 -az \ $HOME atticserve:/mnt/store/backup/$SHORTHOST At some point it tries to sync the following

I'm getting a 'Forbidden' when accessing dovecot.org.. Have we been rooted, or is this scheduled maintenance, or..? -Michael

hi All, Re below - thanks for the replies to the fsck question. I have run fsck -r /data and this eventually completed with several changes made. Now I am getting the following error from the qla2xxx driver on boot . . . qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. . etc . It looks

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

We have 2 ocfs2 filesystems on our 6 node cluster running OEL5.10 that were created before indexed-dirs were active by default. We were having lag in accessing sub directories that contained 10s of thousands of files, so thought adding the indexes would help, and it did for D/Q, we ran into this in our PROD environment. [root at sahp9465 ~]#cat /etc/redhat-release Red Hat Enterprise Linux

Hi, I have read this thread and want to say that I have expirienced the same problem. Once, when I was loged in, one of my filesystems ( root filesystem :( ) became read-only with the same symptoms. But results was more tragic. Almost in each directory avg. 10% of files had incorrect attributes, owner, links, etc. But filenames was correct. So, I was obliged to re-create root filesystem :(

Hi! I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it. One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in