similar to: ext3 hack: using the journal to replicate a filesystem

Hi all, I'm trying to synchronise a whole directory tree using rsync, from a server named "dev", to the three servers named "w1, w2, w3", hidden behind the server named "prod". So I issued the following command, which failed: dev:~# rsync -avz -e 'ssh prod ssh w2' /users/prod/ root@prod:/home/ bash: prod: command not found rsync: connection

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

Good morning, we've recently had some strange message in /var/log/syslog. System: debian bullseye, kernel 5.10.0-21-amd64 and 5.10.0-22-amd64 gluster 10.3 The message look like: Apr 27 13:30:18 piggy kernel: [24287.715229] INFO: task glfs_fusenoti:2787 blocked for more than 120 seconds. Apr 27 13:30:18 piggy kernel: [24287.715327] Not tainted 5.10.0-22-amd64 #1 Debian 5.10.178-3 Apr

I don't think the issue is on gluster side, it seems the issue is on kernel side (possible deadlock in fuse_reverse_inval_entry) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bda9a71980e083699a0360963c0135657b73f47a On Tue, May 2, 2023 at 5:48?PM Hu Bert <revirii at googlemail.com> wrote: > Good morning, > > we've recently had some strange

My UPS failed and my server took an 'unscheduled outage' a few weeks ago. The only casualty appears to be a volume I used for backup. I usually maintain data on multiple hard disks, but in this case I errantly had some data (of marginal value) on this file system. At this point, the data is not worth enough for me to send the drive out for data recovery, but it's worth enough to

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

As an alternative to polling the client, as Ryan describes, you could consider piggy-backing the status updates on the back of other ajax responses. Which way you go depends entirely on the nature of your app, in particular: 1. how frequently it generates ajax traffic anyway 2. how long the server-side process is going to take If the server-side process takes, say, 20 seconds, polling is a

Hi Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what Eddy described

[ 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

Hello, I''m very new to ruby, and don''t understand the following error, while trying to auto-install rubyonrails via gem; [root@svrlnweb02 root]# gem install rails --include-dependencies /opt/rubygems/0.8.11/bin/gem:3:in `require'': no such file to load -- rubygems (LoadError) from /opt/rubygems/0.8.11/bin/gem:3 [root@svrlnweb02 root]# type gem gem is

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

Here''s the full error: 1) Error: test_add_message_to_existing_ticket(TicketTest): ArgumentError: Unknown key(s): group /usr/lib/ruby/gems/1.8/gems/activesupport-1.2.4/lib/active_support/core_ext/hash/keys.rb:48:in `assert_valid_keys'' /usr/lib/ruby/gems/1.8/gems/acts_as_paranoid-0.2/lib/acts_as_paranoid.rb:125:in `validate_find_options''

I am trying to use data=journal for my root file system. If I add: Kernel /vmlinuz-2.4.7-10 ro root=/dev/hda2 rootflags=data=journal To my grub.conf file, all I get is a kernel Panic, "EXT2-fs: Unrecognized mount option data. Kernel panic: VFS unable to mount root fs on 01:00" My fstab file is: LABEL=/ / ext3 defaults 1 1 Any suggestions?

Hello what is the limitation of inode and journaling on 32 bit ext3 file system. what about 64 bit. Thanks

hai is there any way to view the contents of ext3 journal form windows? regards ______________________________________ Scanned and protected by Email scanner -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070124/02f1d0a5/attachment.htm>