All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13549] Kernel oops while online resizing of an ext4 filesystem
Date: Mon, 22 Mar 2010 21:51:56 GMT	[thread overview]
Message-ID: <201003222151.o2MLpuWI030555@demeter.kernel.org> (raw)
In-Reply-To: <bug-13549-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=13549





--- Comment #12 from Eric Sandeen <sandeen@redhat.com>  2010-03-22 21:51:35 ---
I'm afraid I've not been able to reproduce it:

create a sparse loopback filesystem:

[root@inode test]# touch fsfile
[root@inode test]# truncate --size 1020054732800 fsfile 
[root@inode test]# ls -lh fsfile 
-rw-r--r--. 1 root root 950G Mar 22 16:28 fsfile
[root@inode test]# mkfs.ext4 fsfile 
mke2fs 1.41.10 (10-Feb-2009)

<at this point I checked that the filesystem size and features are similar to
your fs>

[root@inode test]# ls -lh fsfile 
-rw-r--r--. 1 root root 950G Mar 22 16:28 fsfile

Grow the container by about 50G:

[root@inode test]# truncate --size 1099511627776 fsfile 
[root@inode test]# ls -lh fsfile 
-rw-r--r--. 1 root root 1.0T Mar 22 16:32 fsfile

Resize while mounted:

[root@inode test]# mount -o loop fsfile  mnt/
[root@inode test]# resize2fs /dev/loop0 
resize2fs 1.41.10 (10-Feb-2009)
Filesystem at /dev/loop0 is mounted on /mnt/test/mnt; on-line resizing required
old desc_blocks = 60, new_desc_blocks = 64
Performing an on-line resize of /dev/loop0 to 268435456 (4k) blocks.
The filesystem on /dev/loop0 is now 268435456 blocks long.

No oops ... so I'm not sure what is going on here.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-03-22 21:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13549-13602@https.bugzilla.kernel.org/>
2010-03-20 21:53 ` [Bug 13549] Kernel oops while online resizing of an ext4 filesystem bugzilla-daemon
2010-03-21  8:33 ` bugzilla-daemon
2010-03-22 16:51 ` bugzilla-daemon
2010-03-22 17:00 ` bugzilla-daemon
2010-03-22 19:08 ` bugzilla-daemon
2010-03-22 20:16 ` bugzilla-daemon
2010-03-22 20:26 ` bugzilla-daemon
2010-03-22 20:41 ` bugzilla-daemon
2010-03-22 21:51 ` bugzilla-daemon [this message]
2010-03-23 20:14 ` bugzilla-daemon
2010-03-23 20:50 ` bugzilla-daemon
2010-03-23 21:19 ` bugzilla-daemon
2010-03-27 17:48 ` bugzilla-daemon
2010-03-27 18:26 ` bugzilla-daemon
2010-03-27 19:16 ` bugzilla-daemon
2010-03-27 19:28 ` bugzilla-daemon
2009-06-16  9:13 [Bug 13549] New: " bugzilla-daemon
2009-09-18 15:25 ` [Bug 13549] " bugzilla-daemon
2009-09-18 19:03 ` bugzilla-daemon
2010-03-15 19:35 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201003222151.o2MLpuWI030555@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.