similar to: Ext3 step by step installation procedure

Hi! Does anybody know the limit for filename length on Ext2 filesystem? I suspect, there's no difference under Ext3. Am I right? What about pathname length? Best regards, Bostjan ×××××××××××××××××××××××××××××××××××××××××××××× Bostjan Cargo ~~~~~~~~~~~~~~ SDM - GRAU team ~~~ HERMES Softlab ~~ Nova Gorica office ~~~ ~~~~~~~~~ bostjan.cargo@hermes.si ~~~~~~~~~~

The list has gotten pretty quiet over the last week. As I understand it, we are down to the following big ticket items: 1. Quotas on meta journaling 2. ext3 + LFS 3. Various minor bugs. Is this accurate? -- Keith Barrett Red Hat HA Team

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

I'd been hoping to move all of our site to ssh protocol 2 whilst we are still small enough to do this without serious pain, however the lack of authentication and connection forwarding is making that difficult at present. I see the current (2.2.0p1) code base does not have the code on either client or server side for ssh2 to handle tunneled connections or authentication agent. Is this

You need to disable ?ChallengeResponse? (aka keyboard-interactive) authentication, not password authentication, to protect against this attack. On Jul 22, 2015, at 1:56 PM, Bostjan Skufca <bostjan at a2o.si> wrote: > > And to answer your question about what to do, you have three options: > - disable access to ssh with a firewall > - disable password authentication > -

Perfect, thanks. This winds up working for me (as far as I've tested so far.) Match exec "ping -q -c 1 -t 1 %n | grep '192\.168\.'" StrictHostKeyChecking no UserKnownHostsFile none On Wed, Aug 26, 2015 at 11:47 PM, Bostjan Skufca <bostjan at a2o.si> wrote: > (+cc list) > > You could use something in the following manner: > > Match originalhost *

Hello, I am using kernel version 2.4.7-10 I upgraded one of the ext2 partition to ext3. the partitions are nearly empty. I ran a program to create empty files, having names in lexicographical order. The time taken to create empty files (100 .. 100000) is same on an ext2 partition and a ext3 partition. Can anyone pls. tell me why there is no difference in the time taken. Is the htree algo.

As an experiment I set up Challenge/response authentication on a Linux system with PAM using a pam_opie module (this module works fine with console logins and su). I can log into the box using the opie password, *but* it does not give me the challenge - which can make things a little tricky :-) I can well believe this might be a fault in the PAM pam_opie module I am using, so has anyone got

Is there any more docs on this other then the blurb on beta.redhat.com? I got a spare non-critical victim err... test machine I want to try this on and have all the RPMS, but would really like to chew on a little more detail before I leap. Regards, Henri -- "People die." --The Cynic's Book of Wisdom

On Sun, Aug 30, 2015 at 6:57 AM, Bostjan Skufca <bostjan at a2o.si> wrote: > Nico, > > those were my thoughts, exacly, except that I was thinking about using "dig > +short HOST | ..." which has the cleanest output of all. Excellent point. I like it! It can get a bit confusing with round-robin DNS, which can give multiple responses. > But there is that initial

On Fri, Aug 28, 2015 at 8:48 AM, Bostjan Skufca <bostjan at a2o.si> wrote: > On 27 August 2015 at 05:01, Damien Miller <djm at mindrot.org> wrote: >> Yeah, it's unfortunately quite difficult to implement address matching >> in ~/.ssh/config because of the interplay of Host matching, Hostname >> directives, hostname canonicalisation*, proxy commands, hosts

Stephen et al, You may remember me raising the point that the new e2fsprogs (1.25 as I remember) griped about old journals not having all the appropriate fields zeroed. I've just discovered that the RH 7.2 installer produces journals (ie on partitions created as ext3 from within the installer) that flag these warnings with a modified 1.25 e2fsck (the mods being to clear the errors rather

Long ago, when I wrote the ssh config file on my desktop box, ssh (which might have been the non-openssh one) took 3 possible values for the StrictHostKeyChecking option - yes, no & ask. Today, when I attempted to connect to a new machine, with no DNS entries (so using IP address) from my desktop box, ssh (now 2.3.0p1) SEGVed. Looks like there is some subtle interaction between having an

I appear to have a broken filesystem on this box to the point where I am probably going to rebuild the system since I have lost trust in it.... I was wondering if there was any reasonable postmortum work I could do on it before it gets rebuilt. History is that the laptop has a much mauled partition set on it - initially it came with 100% win2k, I then shrunk that and added linux (a RH71 install

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

I think I wrote not very clearly. I say ''swap in domU will save in case lag or little mistake with balloon''. If course, there is no any kind of ballooning for dom0. Right now we running pretty much VMs for our cloud services and we use heavy memory management (it grabs and gives memory with lag less then second depends on usage in customers VM). And we have some statistics

Hi Stephen, I posted a similar report on linux-kernel a month ago, but didn't hear anything new from you. So I try it again in this list, this time with some additional info: Using a stock 2.2.17 kernel with NFS-patches and ext-0.0.3b I can reliably lockup the kjournald when extracting two or three tar.gz files (e.g. kernel tar-balls) onto a ext3 filesystem with activated quotas. This

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

Hi, I just started testing ext3 and perhaps I missed some docs explaining how to convert system partition other than /, like /usr for example . As I have 2 Linux versions on my test machine, I managed to convert /usr by entering the mount -o journal=NNN command from the second OS, but I don't like it. Any suggestions or docs to look at? Thanks in advance Vieri

Fellow riders of the bleeding edge of ext3 technology, I've been playing with ext3 on my workstation. For the most part it has worked very well, but right now I have a non-functional system. I've got patches out the wazoo on this kernel - 2.2.18 + Alan's 2.2.19pre13 + ext3-0.0.6a + i2c-2.5.5 + lm_sensors-2.5.5 + udf-0.9.3. Here is the output I get: EXT3-fs: WARNING: recovery