On Fri, 8 Jun 2007 01:08:12 -0600
Andreas Dilger <[EMAIL PROTECTED]> wrote:
> On Jun 07, 2007 23:45 -0500, Jose R. Santos wrote:
> > The jbd2-debug file used to be located in /proc/sys/fs/jbd2-debug, but
> > create_proc_entry() does not do lookups on file names with more that one
> > directory de
I just noticed while looking through ext4-delalloc-extents-48bit.patch in
git that it is doing all of the bit shifting explicitly, instead of using
the ext_pblock() and ext_store_pblock() helpers...
It also appears that some of the extent code is using "ee_len" directly
instead of the ext4_get_act
In addition to the comments already posted:
> +/* check it manually as using LUKS_read_phdr from libcryptsetup
> + * prints too many warnings if it isn't a luks partition and would add a
> + * dependency on the lib */
> +static int probe_luks(struct blkid_probe *probe,
> +struc
On Fri, 8 Jun 2007 01:08:12 -0600
Andreas Dilger <[EMAIL PROTECTED]> wrote:
> On Jun 07, 2007 23:45 -0500, Jose R. Santos wrote:
> > The jbd2-debug file used to be located in /proc/sys/fs/jbd2-debug, but
> > create_proc_entry() does not do lookups on file names with more that one
> > directory de
This I/O manager saves the contents of the location being overwritten
to a tdb database. This helps in undoing the changes done to the
file system.
The call sequence involve
set_undo_io_backing_manager(unix_io_manager);
set_undo_io_backup_file("/tmp/test.tdb");
retval = ext2fs_open2(dev_name, 0,
On Jun 07, 2007 23:45 -0500, Jose R. Santos wrote:
> The jbd2-debug file used to be located in /proc/sys/fs/jbd2-debug, but
> create_proc_entry() does not do lookups on file names with more that one
> directory deep. This causes the entry creation to fail and hence, no proc
> file is created. Th
