similar to: how does ext3 handle no communication to storage

Hi - We have had 3 rather major occurances of ext3 filesystem corruption lately, i.e. so bad we couldn't event mount, and fsck didn't help. I am looking for pointers, that could help us investigate the root cause. In general... We are running RedHat WS 3 Update 6, 2.4.21-40.2.ELsmp or 2.4.21-37.ELsmp We have a small SAN system that looks like this

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose

Hi folks -- My machine is a RHEL 3 with 2.4 kernel installed - with some large ext3 filesystems on drives connected internally ( >200G) Now, When this system crashed (for eg:- a CPU panic /hardware error ) - e2fsck on this filesystem seems to be taking a long time to return thereby adding to the overall downtime of this system. could there be any workarounds for my issue? say for

One question that keeps coming up in my discussions about ZFS is the lack of user quotas. Typically this comes from people who have many tens of thousands (30,000 - 100,000) of users where they feel that having a file system per user will not be manageable. I would agree that today that is the case however I personally don''t see this as an insurmountable problem. However the questions

Hello, I was told that work had been done to use R with the CERN developed framework "ROOT" but can't find anything on your site. Please point me to whatever has been done. Sebastian White Sebastian White, Physics Deprtment Brookhaven National Laboratory Offiice: 631-344-5488 cell: 516-443-0039 email: swhite at bnl.gov Sebastian.White at cern.ch

Hello, I just need a little clarification regarding applying the ext3 patch to the latest kernel. I have 2.4.7-10 that came with RH 7.2. I have ext3 running. I need to upgrade those (to get some USB device working). So I got the latest kernel, 2.4.14, patched it with the ext3-2.4-0.9.15-2414 patch, picked ext3 from 'make xconfig', built the kernel, but the new stuff in /boot, etc.,

Hi all, Looks like I'm going to make the trip over to Astricon next month, but finances being what they are and since I'll be paying for my own flight from the UK, I'm trying to cut down on costs. The problem I've got is that the hotel is about 4 miles from the nearest public transportation (Brookhaven station) and the shuttle bus is only for hotel residents. Hiring a car seems

Hi all i installed Redhat beta Roswell, then i updated to Kernel 2.4.8 patched him and installed the newest util-linux + e2fprogs without any custoumized Options. Bootloader is Grub. Now when i boot he says mount -O or -0 is an invalid Option. tune2fs -j /dev/hdXX says "The filesystem already has a journal" lsmod says that no jbd or ext3 Modules is loadet but i have pachted the Kernel

Good morning. I am trying to do a dhcp/pxelinux network install for redhat linux. I have a new Dell computer with a Broadcom NetXtreme 57xx Gibabit controller. I am getting the following errors: Getting Kickstart file. ASSERT: no network device in ChooseNetworkInterface No network drivers for doing kickstart unable to bring up network. I've searched this lists archives for the word ASSERT

Hello , i want to create a script that should automatically free the proxy partition i.e /var. I am able to create that script. But the problem is that i don't know through which variables i can check my partition's space that show me full detail i.e remaining size, etc. One for that is df -h and other fdisk -l /dev/hdxx. But when i will use if state then which

Hi, I've run many time e2fsck, but in a special dir ls tells me: ls: r?cksendung-wlan.dvi: No such file or directory ls: baf?g_r?ckmeldung.latex: No such file or directory ls: finpr?f.pdf: No such file or directory $ cat finpr?f.pdf cat: finpr?f.pdf: Datei oder Verzeichnis nicht gefunden I don't know what to do? How can I find the failure? If I cat the files with debugfs, I see the

Hi all, I have a relationship (no really!) class RiskMatrix < ActiveRecord::Base has_many :severities, :order => :position, :uniq => true end class RiskFactor < ActiveRecord::Base belongs_to :risk_matrix validates_presence_of :descriptor, :example validates_uniqueness_of :descriptor, :example, :scope=> :risk_matrix_id end class Severity < RiskFactor

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

When SEV is enabled in domcapabilities does that just mean any of SEV, SEV-ES, SEV-SNP is possible on the hardware? Similarly, does enabling SEV as a launchSecurity option in a domainXML mean that whichever SEV is available will be enabled? And if the guest policy has the ES flag set, it will not be created unless ES is enabled? Sorry if these questions don't make sense or are ill-formed.

I have tried everything to compile a new kernel on my 7.2 base system. I have used 2.4.13-ac6 and 2.4.13 w/ ext3 patch. I have compiled with ext3 built-in and with ext3 as module (with the initrd). I have a SCSI system so I have done the previous variations with both SCSI support built-in and modular (with the initrd). The error I get is: Remounting root filesystem in read-write mode: mount: no

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

From: Joerg Roedel <jroedel at suse.de> Hi, here is a new version of the SEV-ES Guest Support patches for x86. The previous versions can be found as a linked list starting here: https://lore.kernel.org/lkml/20200824085511.7553-1-joro at 8bytes.org/ I updated the patch-set based on ther review comments I got and the discussions around it. Another important change is that the early IDT

From: Joerg Roedel <jroedel at suse.de> Hi, here is a new version of the SEV-ES Guest Support patches for x86. The previous versions can be found as a linked list starting here: https://lore.kernel.org/lkml/20200824085511.7553-1-joro at 8bytes.org/ I updated the patch-set based on ther review comments I got and the discussions around it. Another important change is that the early IDT

From: Joerg Roedel <jroedel at suse.de> Hi, here is the fourth version of the SEV-ES Guest Support patches. I addressed the review comments sent to me for the previous version and rebased the code v5.8-rc5. The biggest change in this version is the IST handling code for the #VC handler. I adapted the entry code for the #VC handler to the big pile of entry code changes merged into