Displaying 7 results from an estimated 7 matches for "s_es".
Did you mean:
es_es
2005 Feb 15
1
[PATCH] ext3: Fix sparse -Wbitwise warnings.
...primary[i]->b_blocknr, gdbackups,
blk + primary[i]->b_blocknr); */
@@ -675,7 +675,7 @@
"can't update backup for group %d (err %d), "
"forcing fsck on next reboot\n", group, err);
sbi->s_mount_state &= ~EXT3_VALID_FS;
- sbi->s_es->s_state &= ~cpu_to_le16(EXT3_VALID_FS);
+ sbi->s_es->s_state &= cpu_to_le16(~EXT3_VALID_FS);
mark_buffer_dirty(sbi->s_sbh);
}
}
2006 Jan 25
1
EXT3: failed to claim external journal device.
We are having problems remounting an ext3 filesystem using an external
journal device. The filesystem in question was working fine until the
server was rebooted.
This is what we see on dmesg when trying to mount:
EXT3: failed to claim external journal device.
The external journal lives on a LVM2 logical volume and it seems to be
accessible ( we can dumpe2fs and see filesystem information).
2005 Jun 20
0
[patch 2/3] fs/ext3/resize.c: fix sparse warnings
An embedded and charset-unspecified text was scrubbed...
Name: sparse-fs_ext3_resize.patch
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/8e33ffa8/attachment.ksh>
2005 Oct 31
2
What is the history of CONFIG_EXT{2,3}_CHECK?
Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK?
There is code for a "check" option for mount if these options are
enabled, but there's no way to enable them.
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
2001 Mar 28
1
Ext3 and LFS - possible? fatal?
Has anyone tried LFS (ie >2G files support) and Ext3 together?
Are there good reasons why this should/should not work?
I see the RH enterprise kernel patch set specifically does not attempt
both lfs and ext3, but the lfs patches themselves touch some reasonably
localised parts of ext2, so I would hope (without having dived in there
to test), that the ext3 changes would mirror that
2005 Jan 06
0
[2.6 patch] fs/ext3/: possible cleanups
...ing (struct super_block * sb, const char * function,
const char * fmt, ...)
{
@@ -386,7 +371,7 @@
}
}
-void ext3_put_super (struct super_block * sb)
+static void ext3_put_super (struct super_block * sb)
{
struct ext3_sb_info *sbi = EXT3_SB(sb);
struct ext3_super_block *es = sbi->s_es;
@@ -2018,7 +2003,7 @@
* This implicitly triggers the writebehind on sync().
*/
-void ext3_write_super (struct super_block * sb)
+static void ext3_write_super (struct super_block * sb)
{
if (down_trylock(&sb->s_lock) == 0)
BUG();
@@ -2041,7 +2026,7 @@
* LVM calls this function...
2007 Mar 29
3
tune2fs -l stale info
Hello,
I just noticed that 'tune2fs -l' did not returned a "lively" updated
information regarding the free inodes count (looks like it's always
correct after unmounting). It became suprising after an online resizing
operation, where the total inode count was immediatly updated (grown in
my case) but the free inode count was the same: one could deduce that
suddenly a lot of