similar to: in-core inode

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

i too am an idiot.. and request help here's the sccop i originally formatted the drive with 3 partitions and installed rh8 /boot / swap everything worked. my plan was to have this drive only be a data drive so i inatlled rh8 on another drive and mounted this one on /share so /share looked like /share /bin /sbin /mp3 /usr /etc /dev and so on so i deleted all the

Hi. I'm attempting to setup a box here to be a file-server for all my data. I'm attempting to resize an ext3 partition to demonstrate this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

Hi! I'm going to build a maildir-based mailserver with a ~56 gb mail-partition. What blocksize/bytes-per-inode/number of inodes should i use (i don't want to ran out of inodes and don't want to sacrifice too much space for filefragments)? Is there a drawback when lowering the blocksize/increasing the number of inodes (except the maximum filesystem size)? The inodes used by a file is

Hello, I am running kernel 2.6.4 on XScale/ARM with BusyBox. Quite frequently after shutdown I have a number of orphaned inodes on the ext3 filesystem. (I have yet to figure out the precise cause of the orphans, but I believe it has to do with umount failing at shutdown due to a bug in BusyBox init that does not properly kill processes.) It is my understanding the orphaned inode list should be

Hi, I have an ext3 file system created with -T largefile4 option. Now it is running out of inode but it's only about 10% full. - Is there a way now to increase the number of inode without making a new file system? - If not, I am thinking about shrinking the file system, and then use the free up space to create a new file system with more inodes, and move the data over. Since I am

A hardware vendor shipped us a product installed with RedHat 8.0 with all file systems created as ext3. This system has about 800 GB of space which we use for buffering email files (in RFC format). Several weeks into the project and with millions of emails stored, we started seeing "out of inode" (something like that) error messages in the /var/log/messages. Are inodes fixed on ext3

I encountered same error when use Xen3.0.2(source file) on CentOS4.2, after I downgraded to Xen2.0.7(source file), this error disappeared. now, I am using Xen2.0.7 instead of 3.0.2, it works well. --taylor -----邮件原件----- 发件人: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] 代表 xen-users-request@lists.xensource.com 发送时间: 2006年6月15日 5:24 收件人:

I have made some more research and found out the following .. thor:~# df -i Filesystem Inodes IUsed IFree IUse% Mounted on -[cut]- /dev/mapper/vgraid-data 475987968 227652 475760316 1% /data thor:~# strace e2defrag -r /dev/vgraid/data -[cut]- mmap2(NULL, 1903955968, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x46512000 (delay 15 seconds

I'm happy to announce the release of e2fsprogs 1.42. You can download the tarball from here: http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.42.tar.gz Or you can download it from the git repository on git.kernel.org. git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git. Or, you can wait for your favorite distribution to package it. :-) The release notes are attached

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

Add an option ''s'' to set bufsize in logical to inode transition, then we are able to read all the refs to the logical address. Meanwhile, set a max value 64k for the bufsize. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- v2->v3: - use 64k as the upper limit - document command''s options cmds-inspect.c | 23 +++++++++++++++++------ man/btrfs.8.in |

Hi Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

Hello, I'm using a defualt everything install of 7.2 (kernel 2.4.7-10 #1) with a 27 gig ext3 / partition. The problem that I am experiencing is this: If I create more than (about) 3.5 million distinct files on the partition, touch, mkdir, cp and all other file creation methods complain that there is no available space on the disk. A df shows me that the partition is only 65% full.

Hello, yesterday I experienced following problem with my ext3 filesystem: - I had ext3 filesystem of the size of a few TB with journal. I correctly unmounted it and it was marked clean. - I then ran fsck.etx3 -f on it and it did not find any problem. - After increasing size of its LVM volume by 1.5 TB I resized the filesystem by resize2fs lvm_volume and it finished without problem. - But

Ralf Hildebrandt reported[0] the following messages on ext3-users: name_count maxed, losing inode data: dev=00:05, inode=5221 because the filesystem in question is indeed ext3. However, this warning is not generated by ext3 code but by the audit framework. While the origins of these messages are discussed elsewhere[1] the following patch modifies the printks in question so that users know

On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote: > > yesterday I experienced following problem with my ext3 filesystem: > > - I had ext3 filesystem of the size of a few TB with journal. I correctly > unmounted it and it was marked clean. > > - I then ran fsck.etx3 -f on it and it did not find any problem. > > - After increasing size of its LVM volume by

I am building a tool to identify the file that has a specific LBA. The approach I am using is to search through each inode from number 2 up. This approach works well with UFS1 file systems as then preinitialize all the inodes. However, UFS2 does lazy inode initialization so there are always some that are basically garbage. I have not found any relaiable way to determine from the