similar to: Why does file's inode change?

Hi! Is there a way to view ext3 filesystem's maintained journal (in a human-readable-format)? I ask, because i have had a server crash before and now i'm wondering if i might take a look at last things that my server did straight before crash. I guess clarifying log insertions might be lost before buffers were flushed to disk. Thx.

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

I have seen this happen a number of times: Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 kernel: Aborting journal on device sda5. Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 last message repeated 6 times Jun 13 13:58:18 n202 kernel: ext3_abort

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3

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

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets

Hi, The documentation warns about using smaller inodes than 512 bytes on the MDT. If I plan to use a stripecount of one (I have many small files), is it possible to use an inode size of 256 bytes and still use in-inode EAs for metadata ? Thanks /Jakob

hello: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

I've got an approximately 100GB ext3 FS which we recently sized down from 300GB using e2fsadm (with the disc offline obviously). I noticed the following in dmesg the other day: EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14827639 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14041793 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc:

Hi, first of all, apologies if this isn't the right mailing list but it was the best I could find. If you know a better mailing list, please tell me. Today I tried to defrag one of my filesystems. It's a 3.5T large filesystem that has 6 software-raids in the bottom and then merged together using lvm. I was running ext3 but removed the journal flag with thor:~# tune2fs -O ^has_journal

hi! One of our user removed a directory through samba and right after that recreated it. It looks like this now: ?????????? ? ? ? ? ? 20110817 Gluster version is 3.2.2-1ubuntu~ppa1~lucid1 on client (samba server) and the same but Natty on the nodes. It was upgraded from 3.2.1. What is this? If a client try to access it, it freezes up. This is in log: [2011-08-17

Hi, Somehow I've managed to get e2fsck to seg fault.. The filesystem in question started acting very strangely (e.g. filenames changing from music to MuSiC etc) so I rebooted, and since when fsck has crashed every time it has been run. I'm not really sure what any of this means, so I didn't know what debugging output to include, but below is the output of e2fsck. (I would have

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

I decided to start using ext3. My kernel 2.4.15p9. I downloaded and build util-linux-2.11m and e2fsprogs 1.25. I compiled ext3 in the kernel. I started converting my filesystems and thing went ok for the first few. I then started getting the following on each additional filesystem. [root@joker /root]# tune2fs -j /dev/hdc4 tune2fs 1.25 (20-Sep-2001) Creating journal inode: done This filesystem

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

In reflink we update the id info in the disk but forget to update the corresponding information in the VFS inode. So update them accordingly in case we want to preserve the attributes. Reported-by: Jeff Liu <jeff.liu at oracle.com> Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/refcounttree.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)):

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.

On a customer's machine running SuSE 9.2, the size of the occupied space on the harddisk is reported incorrectly by "df -h". After we noticed the problem, I rebooted the machine and had it checked by "e2fsck" (check forced with "tune2fs -C 40", we are not on location). Right after the reboot I proceeded as follows, but I could not find any information about