From: Peter Seiderer <Peter.Seiderer@ciselant.de>
To: linux-kernel@vger.kernel.org
Cc: Ville Herva <vherva@niksula.hut.fi>
Subject: Re: What is the difference between 'login: root' and 'su -' ?
Date: Thu, 8 Nov 2001 09:46:37 +0100 [thread overview]
Message-ID: <20011108094637.B615@zodiak.ecademix.com> (raw)
In-Reply-To: <20011107184710.A1410@zodiak.ecademix.com> <20011107224824.G26218@niksula.cs.hut.fi> <20011107234025.A602@zodiak.ecademix.com> <20011108081006.S1504@niksula.cs.hut.fi>
In-Reply-To: <20011108081006.S1504@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Thu, Nov 08, 2001 at 08:10:07AM +0200
Hello,
in both cases file descriptor 4 is from 'open("/dev/hdc4", O_RDWR) = 4' ....
Peter
On Thu, Nov 08, 2001 at 08:10:07AM +0200, Ville Herva wrote:
> On Wed, Nov 07, 2001 at 11:40:25PM +0100, you [Peter Seiderer] claimed:
> > Mhhh,
> > the strace output from the 'login: root' one (the one which was good)
> > looks the same till the EFBIG place:
> >
> > write(1, "\10\10\10\10\10", 5) = 5
> > write(1, "16/44", 5) = 5
> > _llseek(4, 18446744071562084352, [2147500032], SEEK_SET) = 0
> > write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 32768
> > _llseek(4, 18446744071562117120, [2147532800], SEEK_SET) = 0
> > write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 32768
> > _llseek(4, 18446744071562149888, [2147565568], SEEK_SET) = 0
> > write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 32768
> > _llseek(4, 18446744071562182656, [2147598336], SEEK_SET) = 0
> > write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = 32768
>
> Weird. Perhaps strace gets that wrong and the problem is elsewhere.
>
> Did you make sure that fd 4 is the same _partition_ in both cases (using
> strace)? The only thing I could imagine exposing 2GB limit is writing to a
> file.
>
> > > > zodiak login: seiderer
> > > > Password:
> > > > seiderer@zodiak:~ > su -
> > > > Password:
> > > > zodiak:~ #
> > > > zodiak:~ # mkfs.ext2 /dev/hdc4
> > > > mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> > > > Filesystem label=
> > > > OS type: Linux
> > > > Block size=4096 (log=2)
> > > > Fragment size=4096 (log=2)
> > > > 716672 inodes, 1432116 blocks
> > > > 71605 blocks (5.00%) reserved for the super user
> > > > First data block=0
> > > > 44 block groups
> > > > 32768 blocks per group, 32768 fragments per group
> > > > 16288 inodes per group
> > > > Superblock backups stored on blocks:
> > > > 32768, 98304, 163840, 229376, 294912, 819200, 884736
> > > >
> > > > Writing inode tables: 16/44File size limit exceeded
> > > >
> > > > strace showed that write returned wit EFBIG and the process ended with SIGXFSZ:
> > > >
> > > > write(1, "\10\10\10\10\10", 5) = 5
> > > > write(1, "16/44", 5) = 5
> > > > _llseek(4, 18446744071562084352, [2147500032], SEEK_SET) = 0
> > > > write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768) = -1 EFBIG (File too large)
> > > > --- SIGXFSZ (File size limit exceeded) ---
> > > > +++ killed by SIGXFSZ +++
> > >
> > > Hmm, 18446744071562084352 = 0xffffffff80004000, 2147500032 = 0x80004000...
> > > It looks a tad like llseek's offset_high would have been corrupted...
> > > Strange.
> > >
> > > 1432116 blocks * 4096 bytes/block * 16/44 written = 2133071685.81818 so
> > > 2147500032 looks sane(ish).
>
> -- v --
>
> v@iki.fi
next prev parent reply other threads:[~2001-11-08 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 17:47 Peter Seiderer
[not found] ` <20011107224824.G26218@niksula.cs.hut.fi>
2001-11-07 22:40 ` Peter Seiderer
[not found] ` <20011108081006.S1504@niksula.cs.hut.fi>
2001-11-08 8:46 ` Peter Seiderer [this message]
[not found] ` <20011108104634.T1504@niksula.cs.hut.fi>
2001-11-08 9:00 ` Peter Seiderer
[not found] ` <20011108111330.U1504@niksula.cs.hut.fi>
2001-11-08 10:14 ` Peter Seiderer
2001-11-08 14:20 ` [patch] " Peter Seiderer
2001-11-08 7:31 ` Vitezslav Samel
2001-11-08 15:38 ` Tobias Diedrich
2001-11-08 18:35 ` Peter Seiderer
2001-11-08 14:34 PVotruba
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=20011108094637.B615@zodiak.ecademix.com \
--to=peter.seiderer@ciselant.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/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®