Displaying 5 results from an estimated 5 matches for "ext3_remount".
2005 Jun 20
0
[patch 1/3] fs/ext3/super.c: fix sparse warnings
An embedded and charset-unspecified text was scrubbed...
Name: sparse-fs_ext3_super.patch
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/af49961a/attachment.ksh>
2005 Jan 06
0
[2.6 patch] fs/ext3/: possible cleanups
...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_lockfs (struct super_block *);
-extern void ext3_unlockfs (struct super_block *);
-extern int ext3_remount (struct super_block *, int *, char *);
-extern int ext3_statfs (struct super_block *, struct kstatfs *);
#define ext3_std_error(sb, errno) \
do { \
if ((errno)) \
__ext3_std_error((sb), __FUNCTION__, (errno)); \
} while (0)
-extern const char *ext3_decode_error(struct super...
2005 Feb 15
1
[PATCH] ext3: Fix sparse -Wbitwise warnings.
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
===================================================================
---
2002 Dec 24
0
Cosmetical printk change, remounting problems.
...then tried to remount it rw again but got the
following error:
root@yadda:~# mount -oremount,rw /dev/hdk1
mount: block device /dev/hdk1 is write-protected, mounting read-only
root@yadda:~#
which was accompanied by the following printk's:
ext3_abort called.
EXT3-fs abort (device ide5(57,1)): ext3_remount: Abort forced by user
Do I have to reboot the server to be able to mount the FS rw again or
should a normal umount/mount suffice?
best regards,
michael
2001 Nov 20
1
EXT3-fs error (device ide0(3,9)): ext3_readdir
...ck ?
Remounting rw doesn't work :
root@enterprise:/ #mount -o remount,rw /usr
mount: block device /dev/hda9 is write-protected, mounting read-only
and then in syslog:
Nov 20 19:47:04 enterprise kernel: ext3_abort called.
Nov 20 19:47:04 enterprise kernel: EXT3-fs abort (device ide0(3,9)):
ext3_remount: Abort forced by user
As I already said, the first time ever I had any problems since the very
first versions. Thanks for your great work !
Cheers,
Dirk