All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Writes greater than 64k fails with -ENOSPC
Date: Tue, 29 Jan 2013 17:54:21 +0530	[thread overview]
Message-ID: <5107BF75.704@suse.com> (raw)

Hi all,

I'm looking into a report on 3.0 based kernel (plus stable fixes)
where writes greater than 64k to a NAS (Hitachi NAS) is failing
(simple dd). The problem was not seen with a 2.6.32-ish kernel.
Also, note that the problem is not seen with other Servers such
as Windows 2003 or Windows 8 Servers.

The strace output shows the close() fall fails with -ENOSPC. 

The relevant cFYI snip

Jan 23 08:31:45 vsusix02 kernel: [1003552.227274] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/transport.c: For smb_command 47
Jan 23 08:31:45 vsusix02 kernel: [1003552.227277] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/transport.c: Sending smb:  total_len 127044
Jan 23 08:31:45 vsusix02 kernel: [1003552.345848] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/connect.c: rfc1002 length 0x33
Jan 23 08:31:45 vsusix02 kernel: [1003552.393906] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/cifssmb.c: async write at 1015808 8192 bytes
Jan 23 08:31:45 vsusix02 kernel: [1003552.393911] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/transport.c: For smb_command 47
Jan 23 08:31:45 vsusix02 kernel: [1003552.393914] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/transport.c: Sending smb:  total_len 8260
Jan 23 08:31:45 vsusix02 kernel: [1003552.479378] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/connect.c: rfc1002 length 0x33
Jan 23 08:31:45 vsusix02 kernel: [1003552.481215] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/connect.c: rfc1002 length 0x33
Jan 23 08:31:45 vsusix02 kernel: [1003552.481260] /usr/src/packages/BUILD/kernel-default-3.0.42/linux-3.0/fs/cifs/file.c: Flush inode ffff88004e1655c0 file ffff8800379d48c0 rc -28


The problem seems to be that during close(), we try to flush the
buffers by calling cifs_flush() which in turn will call
filemap_write_and_wait() to wait on the pages under writeback to
complete. do_writepages() will invoke cifs_writepages() which is 
perhaps returning -ENOSPC and it is propagated back.

There are no quota restrictions or disk space problems. The
tcpdump output doesn't show any errors during the write or close.

I'm not sure what could be causing the problem and would
appreciate any clues or debugging suggestions.

Thanks

-- 
Suresh Jayaraman

             reply	other threads:[~2013-01-29 12:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:24 Suresh Jayaraman [this message]
     [not found] ` <5107BF75.704-IBi9RG/b67k@public.gmane.org>
2013-01-30  0:29   ` Writes greater than 64k fails with -ENOSPC Jeff Layton
     [not found]     ` <20130129192913.4942c635-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-01-30 14:06       ` Tom Talpey
     [not found]         ` <614F550557B82C44AC27C492ADA391AA044F2484-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-01-30 14:37           ` Jeff Layton
     [not found]             ` <20130130093729.736ad582-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-01-30 16:06               ` Tom Talpey
     [not found]                 ` <614F550557B82C44AC27C492ADA391AA044F2E62-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-01-30 17:49                   ` Jeff Layton
     [not found]                     ` <20130130124932.419f2d36-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-01-30 18:07                       ` Tom Talpey
2013-01-31  9:52                   ` Suresh Jayaraman
     [not found]                     ` <510A3ECF.2080505-IBi9RG/b67k@public.gmane.org>
2013-01-31 11:24                       ` Jeff Layton
     [not found]                         ` <20130131062400.6aa8fb6d-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-02-07  8:52                           ` Suresh Jayaraman
     [not found]                             ` <51136B34.30609-IBi9RG/b67k@public.gmane.org>
2013-02-07 11:50                               ` Jeff Layton
     [not found]                                 ` <20130207065018.0c18868e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-02-07 13:37                                   ` Tom Talpey
     [not found]                                     ` <614F550557B82C44AC27C492ADA391AA044FC781-Jfd81uAzPQsmBPcf4Gwd0Fir+X/St4rqwBk/1ggFUS45P9zcU8sUGwC/G2K4zDHf@public.gmane.org>
2013-02-07 13:55                                       ` Jeff Layton
2013-01-31  9:47       ` Suresh Jayaraman
     [not found]         ` <510A3DB0.1040004-IBi9RG/b67k@public.gmane.org>
2013-01-31 11:21           ` Jeff Layton

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=5107BF75.704@suse.com \
    --to=sjayaraman-ibi9rg/b67k@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.