similar to: df report

Hi, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my

Hi, We are using the latest ocfs with 11 nodes: OCFS2 Node Manager 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 0f78045c75c0174e50e4cf0934bf9eae) OCFS2 DLM 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 4ce8fae327880c466761f40fb7619490) OCFS2 DLMFS 1.4.1 Tue Dec 16 19:18:05 PST 2008 (build 4ce8fae327880c466761f40fb7619490) OCFS2 User DLM kernel interface loaded But we are unable to create files

Hi, I have installed Red Hat Linux 7.3 with ext2 file system and I have multiple partition. I converted them to ext3 using following command. tune2fs -j -i 0 /dev/hdaX And I modified /etc/fstab as below. LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

greetings. i have been three days now trying to add ext3 to an existing suse-7.3 machine. i am using suse's own 2.4.13 kernel source. here is what i have done: following install, i ran tune2fs -j /dev/hda2 (also hda3 and hda4). .journal files were created on each partition, apparently uneventfully. wishing to avoid ai irreversable situation, i initially edited /etc/fstab thusly:

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your

Background: This is a dual boot (Windows XP and CentOS 5.2 (32 bit) box. There were four (4) NTFS partitions. The C partition got full. I deleted the 4 NTFS partitions and did a clean install of Windows XP, into one (1) NTFS partition. I knew that I would need to install GRUB again and I did that, using the CentOS 5 Installation DVD. When I tried to boot into Linux, no joy. this is the GRUB error

I recently installed CentOS 5.1 on a DL71 ASI notebook. After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot. Any help or suggestions to fix this would be much appreciated CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686 # grub.conf

Hi, Apologies in advance for any breaches of netiquette, I couldn't find any guidelines about submission to this forum but I'd be grateful for your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. I get the following messages... journal_bmap_Ra7a5f568: journal block not found at offset 12 on ide0(3,1) Aborting journal on device ide0(3,1)

Hi, I'm currently experimenting with software RAID1 on a spare PC with two 40 GB hard disks. Normally, on a desktop PC with only one hard disk, I have a very simple partitioning scheme like this : /dev/hda1 80 MB /boot ext2 /dev/hda2 1 GB swap /dev/hda3 39 GB / ext3 Here's what I'd like to do. Partition a second hard disk (say, /dev/hdb) with three

Hi, Stephen and Jeff, Thanks. But the problem got debugged&fixed, the answer was post on fedora-list about 2 weeks ago. The problem is: the /etc/blkid.tab file works as an old unappropriate disk partitions cache for fsck|blkid commands when stystem image is installed to a different arch (scsi->ide) machine, the old cache will mislead fsck|blkid at the first run and only the first run,

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

Dear Mailinglist, this morning I had a very strange problem with my SuSE Groupware-Server SLOX 4.1. The webmail-access was very slow and even with thunderbird the access to my mailboxes was not okay. I rebooted the whole system, but the problem still was there. I thought, this may be a problem with cyrusd, but I realized, that the error was somewhere deeper in the system, maybe in the

Hello guys, I have some difficulties to understand what really are the numbers behing "df" and tune2fs. You'll find the output of tune2fs and df below, on which my maths are based. Here are my maths: A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It also tell me that the size of one block is 4096 (bytes if I'm not wrong?). So my maths tell me that the disk

Hi, I''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)

Hello. I am trying to boot CentOS 4 from a copy of an ext3 software RAID 1 filesystem (md) which has been copied to a normal ext3 filesystem (hd). I am almost getting there, exept that the system hangs after booting the kernel. I copied the datas from the /boot and / partitions to two similar partitions on the backuped disk with mirrordir (can also be done with cp or dd). I have setup the new

Thanks for you help. I also tried adding some other informations as you suggest: I can also take into account: - "Reserved block count: XXXXXXX" from tune2fs that gives me the number of blocks reserved for root - Reserved GDT blocks: XXX But I didn't thought about the FS journal. How can I gather information about it? (it's size and any other information?) 2013/9/16

On 9/16/13 5:16 AM, Nicolas Michel wrote: > Hello guys, > > I have some difficulties to understand what really are the numbers > behing "df" and tune2fs. You'll find the output of tune2fs and df > below, on which my maths are based. > > Here are my maths: > > A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It > also tell me that

I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a