Displaying 8 results from an estimated 8 matches for "ext3_warning".
2006 May 03
0
We hit ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");
Dear ext3-users,
we hit this condition in fs/ext3/inode.c:ext3_block_to_path()
if (i_block < 0) {
ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0");
occasionally on two identical PATA-IDE disks copied over per filesystem-rsync.
What is the impact of this condition?
- Kernel was 2.6.13.4, CONFIG_LBD is not set but CONFIG_HIGHMEM4G=y
(I can provide further details,...
2006 May 26
1
[PATCH - 2.6.17-rc5] ext3: Fix missed mutex unlock - unroll
...at intel.com>
Signed-off-by: Andrew Morton <akpm at osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh at suse.de>
---
--- a/fs/ext3/resize.c
+++ b/fs/ext3/resize.c
@@ -767,6 +767,7 @@ int ext3_group_add(struct super_block *s
if (input->group != sbi->s_groups_count) {
ext3_warning(sb, __FUNCTION__,
"multiple resizers run on filesystem!");
+ unlock_super(sb);
err = -EBUSY;
goto exit_journal;
}
2004 Jul 22
1
How to interpret corruption error message
(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
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 Feb 15
1
[PATCH] ext3: Fix sparse -Wbitwise warnings.
...nt gdbackups;
struct ext3_iloc iloc;
- __u32 *data;
+ __le32 *data;
int err;
if (test_opt(sb, DEBUG))
@@ -408,7 +408,7 @@
goto exit_bh;
}
- data = (__u32 *)dind->b_data;
+ data = (__le32 *)dind->b_data;
if (le32_to_cpu(data[gdb_num % EXT3_ADDR_PER_BLOCK(sb)]) != gdblock) {
ext3_warning(sb, __FUNCTION__,
"new group %u GDT block %lu not reserved\n",
@@ -510,7 +510,7 @@
struct buffer_head *dind;
struct ext3_iloc iloc;
unsigned long blk;
- __u32 *data, *end;
+ __le32 *data, *end;
int gdbackups = 0;
int res, i;
int err;
@@ -527,15 +527,15 @@
}
blk...
2005 Jan 06
0
[2.6 patch] fs/ext3/: possible cleanups
...ar *, int);
extern void ext3_abort (struct super_block *, const char *, const char *, ...)
__attribute__ ((format (printf, 3, 4)));
-extern NORET_TYPE void ext3_panic (struct super_block *, const char *,
- const char *, ...)
- __attribute__ ((NORET_AND format (printf, 3, 4)));
extern void ext3_warning (struct super_block *, const char *, const char *, ...)
__attribute__ ((format (printf, 3, 4)));
extern void ext3_update_dynamic_rev (struct super_block *sb);
-extern void ext3_put_super (struct super_block *);
-extern void ext3_write_super (struct super_block *);
-extern void ext3_write_super_l...
2001 Oct 28
4
Extended Attributes and Access Control Lists
Hello,
I have today released an initial version of extended attributes and access
control lists for ext3 (patch against the 2.4.13-ac3 kernel). Eric Jarman
<ejarman@acm.org> has contributed a lot to this effort.
Since I'm not very much into the innards of ext3, can some of you please
take a look at the patch, and see whether it contains any flaws (and tell
me which flaws)? Thanks!
The
2006 Jul 26
5
linux-2.6-xen.hg
Hi,
Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being
updated? if not, what''s the preferred Linux tree to track that has all
of the Xen bits?
Thanks,
Muli
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel