From: "Łukasz Oleś" <lukasz.oles@open-e.com>
To: xfs@oss.sgi.com
Cc: Artur Piechocki <artur.piechocki@open-e.com>
Subject: xfsprogs 2.x vs 3.x logsize changed
Date: Wed, 17 Nov 2010 15:49:04 +0100 [thread overview]
Message-ID: <201011171549.04806.lukasz.oles@open-e.com> (raw)
Hi,
I'm upgrading xfsprogs from 2.10.1 to the latest 3.1.4 version. I noticed that
when I'm creating large lvm volume (2T) the log size is almost 1G in the old
version it was 128M.
I know I can manipulate this value with -lsize option, but I'm wondering why
this difference is so huge?
On this volume I have one sparse file which is exported by iSCSI Target. I
have script which calculates for me "seek" value for dd command and now it
returns me wrong values.
Can I stay with the old log size or maybe there are some good reasons to use
new values?
Regards,
Łukasz Oleś
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-17 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 14:49 Łukasz Oleś [this message]
2010-11-17 21:22 ` xfsprogs 2.x vs 3.x logsize changed Michael Monnerie
[not found] ` <4CE41315.8070402@sandeen.net>
2010-11-18 9:49 ` Łukasz Oleś
2010-11-18 14:39 ` Eric Sandeen
2010-11-19 1:04 ` Dave Chinner
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=201011171549.04806.lukasz.oles@open-e.com \
--to=lukasz.oles@open-e.com \
--cc=artur.piechocki@open-e.com \
--cc=xfs@oss.sgi.com \
/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.