From: Eunbong Song <eunb.song@samsung.com>
To: Chanho Min <chanho.min@lge.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hyojun.im@lge.com" <hyojun.im@lge.com>
Subject: Re: RE: [PATCH] lib : lz4 using put_unaligned_le16 instead of put_unaligned
Date: Tue, 22 Jul 2014 08:12:06 +0000 (GMT) [thread overview]
Message-ID: <29247639.448531406016725460.JavaMail.weblogic@epml02> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1557 bytes --]
Hello.
>Can you check if this patch fix your problem also?
Unfortunately your patch does not fix my problem. My test logs are as follow.
I did the same test with lzo compression algorithm and with my patch, and
these work well.
debug_shell:/user> echo 1 > /sys/block/zram0/reset
debug_shell:/user> echo lz4 > /sys/block/zram0/comp_algorithm
debug_shell:/user> echo 520M > /sys/block/zram0/disksize
debug_shell:/user> mkfs.ext4 /dev/zram0
mke2fs 1.41.4 (27-Jan-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
33280 inodes, 133120 blocks
6656 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=138412032
5 block groups
32768 blocks per group, 32768 fragments per group
6656 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
debug_shell:/user> mount /dev/zram0 /mnt/
EXT4-fs (zram0): unsupported inode size: 272
mount: wrong fs type, bad option, bad superblock on /dev/zram0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Thanksÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2014-07-22 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 8:12 Eunbong Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-23 4:55 RE: [PATCH] lib : lz4 using put_unaligned_le16 instead of put_unaligned Eunbong Song
2014-07-22 2:17 Eunbong Song
2014-07-22 2:27 ` Greg KH
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=29247639.448531406016725460.JavaMail.weblogic@epml02 \
--to=eunb.song@samsung.com \
--cc=chanho.min@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=hyojun.im@lge.com \
--cc=linux-kernel@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.