search for: golinux

Hi, We will have to go and use SuSE (30 servers) just because ext3 filesystem cannot be increase while the filesystem is mounted. I Don't understand why RedHat do not support filesystems that can do thing that ext3 cannot do. When is RedHat going to understand that in a production environnement (30 servers that is seems will be SuSE) we need extend filesystem online. IBM JS,

Anybody know a way to enlarge a filesystem ext3 without having to unmounted it, when they are still space left in the volume group (when using LVM) ? I will be running large production linux system running Oracle. I can't stop the database everytime I have to enlarge a filesystem. We can do it with all others filesystems (JFS, REISERSFS and XFS) when they are created in a volume group. Why

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

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

Hi all I am having some trouble using the ext2online utility, I have reduced the problem down to its simplist form, and it goes soemthing like this: Start with a regular msdos labelled disk (I have tried lvm volumes): Command (m for help): p Disk /dev/sdb: 18.3 GB, 18351967232 bytes 64 heads, 32 sectors/track, 17501 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot

Helping a friend fix a computer that was having severe, weird troubles. Reformatted (from XP) and installed Fedora. Install went ok, on first boot, however, filesystem was READONLY for some reason. Knew hard drive was suspect, so I e2fsck'd it over and over all night long, fall asleep next to the computer. This morning, Fedora boots fine, login not a problem, so I shut down and fsck it again,

boy, if you really care about your problem, *USE* ext3-users: > oh, and please respond on-list, perhaps other ppl are curious > about some details too ;) really. Tobias Amon schrieb: > Hi, > > I use e2fsprogs version 1.5.2 (I think) http://e2fsprogs.sourceforge.net/ exists, latest version is 1.35. > I got another solution. Yast, which came with Suse > is not able to

Hello Is it possible to externalize the journal of an already existing (journal inside) ext3 FS ? Here's what I did to create a new FS with external journal for /dev/emcpowerl2 on /dev/emcpowerl2 mke2fs -O journal_dev /dev/sda10 mke2fs -J device=/dev/sda10 /dev/emcpowerl2 it works perfectly , but can I do the same whitout reformating the original FS; /dev/emcpowerl1 which is in

i want to use Ext3 as journal file system in a server, and there are several requirements: 1,the largest file should be no smaller than 1TB 2,the largest file syetem should be no smaller than 4TB 3,the max file name should be no less than 255 bytes does Ext3 fix it? or how could i do to solve this requirements? Thanks for your patience and expertise!

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

(sort-of xposted from linux-kernel) Hi, I am wondering how to interpret this error message, which popped up on a 2.4.26 SMP x86 box two days ago: EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck The problem is, the error message doesn't

...Drive C] "Path" = "/mnt/win_c" "Type" = "hd" "Label" = "C" "Device" = "/dev/hda1" "FS" = "win95" I expect this is a problem with my filesystem setup or my OS. This only happened with Mandrake 8.0 - GoLinux and RedHat worked fine. I'm really frotzed in the head over this. Please heal my perception. arnim

Hello-- We have a system where a central server formats removable hard disks, which are then booted in an embedded system running a highly modified RH9. The removable disks themselves contain boot, root, and data filesystems. The problem we've encountered after upgrading to FC3 / kernel 2.6 on the central server is that the 2.4 kernel in the embedded system cannot read the root filesystem,

Hi, If the ext3 file system maximum size updated or it is still 4TB for 2.6.* kernel? The site at http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html says that it is 4TB yet, but I would like to know if it is possible to create and use stable & easy-to-fix (or at least as stable & easy-to-fix as ext3) file systems as big as 100TB for 32 bit Linux architecture? Any experience

Hi users, I was working with GNU parted and got some changes in the partition and the system crashed. I had to freshly install RH Linux 9 again as it didn't detect the linux installation. Now the problem is /dev/hda is mounted but not showing any data files. It has full of data originally. Anyhow Can i recover those data. I didnt format any of the hard drive expect the root partition for

Given that no 1.36 has appeared from Fedora Core, I thought I would create the rpm myself. I took the 1.35-11.2 src.rpm from FC3 and updated the spec file for 1.36. However, the build fails. Has anyone successfully created a 1.36 rpm for FC3? If so, what did you need to do? Gene

Greetings all, I am curious if anyone knows why utilities such as 'GNU shred' (part of coreutils) and 'wipe' say they are not effective on journalled file systems- especially EXT3. Is it because you can't "guarantee" that the journal has been flushed/wiped (i.e. you have the journal 'between' you and the actual data blocks on the physical disk), or because

I've got a 3.3TB ext3 on a FC3 64-bit system, running kernel 2.6.10-1.766FC3smp. I create the partition with parted 1.6.21, and I make the fs via: mkfs.ext3 -m1 -b 4096 -T largefile4 /dev/sda1 Works fine. bonnie++ running on it multiple times for days on end, no problems. However, I do the exact same setup on a RHEL4-AS i686 system, 32-bit, and the fs is totally hosed, get all kinds of

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> --- fs/ext3/resize.c | 20 ++++++++++---------- fs/ext3/super.c | 8 ++++---- include/linux/ext3_fs.h | 2 +- 3 files changed, 15 insertions(+), 15 deletions(-) Index: linux-warnings/include/linux/ext3_fs.h =================================================================== ---

A few wild ideas/questions : 1) Is there a way to check the size of the journal of an ext3 filesystem ? I mean - the actually used size ; not the total size of the journal. 2) Would it be difficult to implement "freeze" of ext3 filesystem - that is, blocking all I/O to the filesystem until it's "unfrozen" (XFS can do that), for two purposes : A/ allowing