similar to: Crypto file systems using ext3

Hi, Since upgrading to 2.4.14 with the ext3 patch, I've been getting the following on bootup: VFS: Mounted root (ext3 filesystem) readonly. change_root: old root has d_count=5 Trying to unmount old root ... invalidate: busy buffer invalidate: busy buffer invalidate: busy buffer invalidate: busy buffer invalidate: busy buffer okay Is the invalidate busy buffer bit anything to worry about?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'd like to put a 60GB hard disk into Gateway 2000 Pentium 150 (from '96 or '97 or so I think) running FreeBSD 4.8 RELEASE. Can anybody tell me how successful this is likely to be? Will I be able to use the full capacity of the drive? I seem to recall that the trick with large hard disks and old BIOSes is to disable the drive in

Hi Darren, Tucker, and openSSH, wolfSSL is a dual licenced software. We have a Commercial option and a GPLv2 option. We provide support to both code sources and are an active part of the open source community. You can freely download our code from our website or visit our development branch on github. https://github.com/wolfSSL/wolfssl. https://wolfssl.com/wolfSSL/download/downloadForm.php

Hello! Certificates from letsencrypt are renewed every three months. Does that mean a MUA has to accept the renewed certificates manually everytime it is renewed? Sorry if this is OT! Greetings Andreas

Hi, We have recently switched from XFS to ext3 do to various corruption scenarios that were witnessed. Does ext3 have something like xfs_growfs for growing the FS to the end of the underlying partition? Thanks, Menny

Hi, I try to convert my RedHat 7.3. partitions from ext3 to ext2. I have found a thread dealing with this issue. Thus: "tune2fs -O ^has_journal /dev/foo" and "e2fsck /dev/foo" will do the magic! This works fine for "/boot" but when I try to convert "/" my kernel panics? The kernel panics message appears shortly after the attempt to startup kjournald. How

I accidentally removed an ext3 partition from the partition table. I know roughly where it started. Is there any way of finding the superblock and reconstructing it? TIA, Dave (Yes I have a backup of the important stuff!)

i have a question on ext3 modes and am not sure if this list is still active

I'm getting ready to add some memory to a server running RH7.3 with ext3. I'm going to need to add more space to the swap partition and so I'll also need to resize an ext3 partition. I've seen some posts by searching the list that the resize2fs should work fine, but the man pages don't mention anything about ext3. Version is: resize2fs 1.27 (8-Mar-2002) Has anyone actually

Hi, I get the error "Operation not permitted" when I try to delete a file as root, see some commands below. - there is no "i" attribute - it's a problem with the files and not the upper directories since I can delete a similar file in the same directory - fsck -f doesn't find any error on the partition - the partition is mounted rw If this is not the right place to

Hey, Thanks for sending me the patch Wiktor, but I was looking for the patch ext3-2.4-0.9.15-2414.gz . If someone has that let me know. Does it work well with kernel 2.4.14 (any installation issues ?) . Why can't I download from http://www.uow.edu.au/~andrewm/linux/ext3 page. If someone can zip the gz patch and email it to me that would be awesome. My email client acts up sometimes.

Tried to convert a 60 gig ext2 disk to ext3. Used tune2fs version 1.22 (it said). The filesystem refused to be converted with that version. Upgraded to 1.25 of e2fsprogs and the problem went away. My two cents. /Benjamin

I've been running RH 72 on my Dell at work. Since I use more than one system and I test things, I forgot that I had the root partition as ext3. That machine has two kernels on it. One is the stock 2.4.7 RH 72 and the other is the new 2.4.17 that I compiled last week. This morning I logged in and typed startx. The kernel responed by coughing up a lung and segfaulted. Couldn't run any

Good morning, I have tried to compile a 2.4.14 kernel (because I have some trouble with the framebuffer and my Toshiba...). Thus, I have downloaded the latest kernel and the ext3 patch. I have used the .config file used for the compilation of my 2.4.13 kernel, but the compilation ends with make[1]: Quitte le répertoire `/usr/src/linux-2.4.14/arch/i386/lib' ld -m elf_i386 -T

I tried it on loop. 1. mount /dev/loop0 /mnt/test -t ext3 2. cp files to 100% full 3. umount /mnt/test 4. fsck.ext3 -f /dev/loop0 Inode xxxxx, i_blocks is xxx, should be yyy. Fix?

I am trying to use data=journal on my root file system. I have separate slices on which journal=data works fine on all of them, except root. I have tried putting rootflags=journal=data on my kernel line in Grub, but I get a kernel panic. I'm missing something simple, I jut know it. It can't be the kernel version because it works on the other slices. My etc/fstab file is as follows:

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

mmmm... stable... :D /usr/src # make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /usr/src # grep audit /usr/src/UPDATING /usr/src # ??? -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz -

pci-iomap.c was (apparently, mistakenly) reintroduced as part of commit 83c2dc15ce824450e7044b9f90cd529c25747ae0 MN10300: Handle cacheable PCI regions in pci_iomap() probably as side-effect of forward-porting the patch from an old kernel. It's not really needed: the generic pci_iomap does the right thing here. The new file isn't compiled so it's safe to drop. Cc: Bjorn Helgaas

pci-iomap.c was (apparently, mistakenly) reintroduced as part of commit 83c2dc15ce824450e7044b9f90cd529c25747ae0 MN10300: Handle cacheable PCI regions in pci_iomap() probably as side-effect of forward-porting the patch from an old kernel. It's not really needed: the generic pci_iomap does the right thing here. The new file isn't compiled so it's safe to drop. Cc: Bjorn Helgaas