From: Jan Kara <jack@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_EXT4_USE_FOR_EXT23 no space left on device
Date: Wed, 27 Nov 2013 23:23:45 +0100 [thread overview]
Message-ID: <20131127222345.GB27330@quack.suse.cz> (raw)
In-Reply-To: <CAMuHMdWgMrNQqq84AK+CGF6VFnLs38O-vyye4MFKNUO7b8iFMw@mail.gmail.com>
On Wed 27-11-13 16:50:14, Geert Uytterhoeven wrote:
> To reduce kernel size, I disabled both CONFIG_EXT2_FS and
> CONFIG_EXT3_FS, and enabled CONFIG_EXT4_USE_FOR_EXT23.
>
> Unfortunately the system behaves badly afterwards. It seems the file system
> is considered full: new files can be created, but no data can be written.
> Note that the file system is almost full, but root can still write more data
> using the real ext3 filesystem driver.
>
> This is a v3.13-rc1-ish kernel.
>
> Diff of dmesg and output of a few operations below:
Thanks for report. Maybe the easiest would be if you gathered fs metadata
using "e2image -r <fs-device>", compressed it and made it available for
download. We can then debug ourselves where the accounting goes wrong.
Honza
>
> --- /tmp/good 2013-11-27 16:47:28.000000000 +0100
> +++ /tmp/bad 2013-11-27 16:47:31.000000000 +0100
> @@ -1,11 +1,13 @@
> -kjournald starting. Commit interval 5 seconds
> -EXT3-fs (hda1): mounted filesystem with writeback data mode
> +
> +EXT4-fs (hda1): mounting ext3 file system using the ext4 subsystem
> +EXT4-fs (hda1): mounted filesystem with ordered data mode. Opts: (null)
> VFS: Mounted root (ext3 filesystem) readonly on device 3:1.
> -Freeing unused kernel memory: 152K (0039d000 - 003c3000)
> +Freeing unused kernel memory: 152K (0037f000 - 003a5000)
> random: nonblocking pool is initialized
> Adding 137800k swap on /dev/hda2. Priority:-1 extents:1 across:137800k
> -EXT3-fs (hda1): using internal journal
> -Unknown key: scancode = 0 ($00), keycode = 'numlock' ($12c)
> +EXT4-fs (hda1): re-mounted. Opts:
> +EXT4-fs (hda1): re-mounted. Opts: errors=remount-ro
> +EXT4-fs (hda1): re-mounted. Opts:
> write cmd 0xE0 (STANDBY IMMEDIATE) not supported
> hda: task_no_data_intr: status=0x41 { DriveReady Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }
> @@ -22,16 +24,9 @@ hda: possibly failed opcode: 0xe0
> reboot: Power down
>
> atari:~# mount
> -/dev/hda1 on / type ext3 (rw,errors=remount-ro)
> -tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> -proc on /proc type proc (rw,noexec,nosuid,nodev)
> -sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> -tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> -devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> -rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> -atari:~# cat /proc/mounts
> +atari:~# cat /proc/mounts
> rootfs / rootfs rw 0 0
> -/dev/root / ext3 rw,relatime,errors=remount-ro,barrier=1,data=writeback 0 0
> +/dev/root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
> tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
> proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> @@ -40,13 +35,9 @@ devpts /dev/pts devpts rw,nosuid,noexec,
> rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
> atari:~# touch /tmp/x
> atari:~# echo hello > /tmp/x
> -atari:~# cat /tmp/x
> -hello
> +-bash: echo: write error: No space left on device
> atari:~# df -h
> -Filesystem Size Used Avail Use% Mounted on
> -/dev/hda1 870M 862M 0 100% /
> -tmpfs 132M 0 132M 0% /lib/init/rw
> -tmpfs 132M 4.0K 132M 1% /dev/shm
> +df: cannot read table of mounted file systems
> atari:~# ls -l /etc/mtab
> --rw-r--r-- 1 root root 331 Nov 27 16:35 /etc/mtab
> +-rw-r--r-- 1 root root 0 Oct 27 15:32 /etc/mtab
> atari:~# poweroff
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-11-27 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 15:50 Geert Uytterhoeven
2013-11-27 22:23 ` Jan Kara [this message]
2013-11-28 10:15 ` Geert Uytterhoeven
2013-11-28 11:33 ` Jan Kara
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=20131127222345.GB27330@quack.suse.cz \
--to=jack@suse.cz \
--cc=geert@linux-m68k.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®