search for: ext3_unlockf

hi all, I intend to write a snapshot module for Ext2/3 file-systems. For that i need to make sure that FS is in consistent state before taking snapshot. For ex. in case of UFS, the superblock has a fs_clean flag which is set to be FSSTABLE to tell that its in consistent state. (otherwise its set to FSACTIVE) I m not able to find any such information for Ext2/Ext3. (The

...gt;>Ext3-users mailing list >>Ext3-users@redhat.com >>https://www.redhat.com/mailman/listinfo/ext3-users >> >> > > for getting state of ext2 filesystem there is a field in super block telling state of ext2. ravindra mahala >>See ext3_sync_super_lockfs(), ext3_unlockfs(), and the LVM >>VFS-locking patch. >>These are used to put the filesystem into a stable state for a >>short time >>until the snapshot is created. >> > >Sir, > >Thanks for your response. >But my problem is a bit different. >Once the snapshot is tak...

...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_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)...

Hello Andrew, I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/ and I have a big problem with: once server is booted on 2.4.20 with your patch, when I want to reboot with /sbin/reboot, server makes a Segmentation fault and it crashs. I tested it on 50-60 servers and it is the same problem. I tested kernel 2.4.20 without your patch: no problem. # uname -a Linux XXXXXX

...super_operations ext3_sops delete_inode: ext3_delete_inode, /* BKL not held. We take it */ put_super: ext3_put_super, /* BKL held */ write_super: ext3_write_super, /* BKL held */ + sync_fs: ext3_sync_fs, write_super_lockfs: ext3_write_super_lockfs, /* BKL not held. Take it */ unlockfs: ext3_unlockfs, /* BKL not held. We take it */ statfs: ext3_statfs, /* BKL held */ @@ -1577,24 +1580,22 @@ int ext3_force_commit(struct super_block * This implicitly triggers the writebehind on sync(). */ -static int do_sync_supers = 0; -MODULE_PARM(do_sync_supers, "i"); -MODULE_PARM_DESC(d...

Hi folks -- My machine is a RHEL 3 with 2.4 kernel installed - with some large ext3 filesystems on drives connected internally ( >200G) Now, When this system crashed (for eg:- a CPU panic /hardware error ) - e2fsck on this filesystem seems to be taking a long time to return thereby adding to the overall downtime of this system. could there be any workarounds for my issue? say for