From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] v9fs mounting in linux
Date: Mon, 20 Nov 2006 17:16:14 -0800 [thread overview]
Message-ID: <F9AA6BA6-2D1E-4928-B285-9D90B0E85807@telus.net> (raw)
In-Reply-To: <13426df10611201627g1d8e0962wf512a11aca15bfc7@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 306 bytes --]
Ah! A debug option. Handy.
But I don't see anything that jumps out and says "error" to me in the
dump. I've attached it.
This is from doing:
echo "foo" > mnt/acme/new/body
The new window appeared, as expected, but no body text made it in,
and the Permission denied came with the write.
[-- Attachment #1.2: foo --]
[-- Type: application/octet-stream, Size: 7066 bytes --]
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_vfs_lookup (31275): dir: def31410 dentry: (new) c7ce3ef8 nameidata: c7050f34
-- v9fs_fid_lookup (31275): dentry: / (c7ce3aec)
-- v9fs_t_walk (31275): fid 0 newfid 1 wname 'new'
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 110
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 22
-- v9fs_write_work (31227): mux ddd39a00 sent 22 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 22 bytes
-- v9fs_deserialize_fcall (31227): size 22 id 111 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 111 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050d20
-- v9fs_t_stat (31275): fid 1
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 124
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 11
-- v9fs_write_work (31227): mux ddd39a00 sent 11 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 83 bytes
-- v9fs_deserialize_fcall (31227): size 83 id 125 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 125 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050d24
-- v9fs_get_inode (31275): super block: df556400 mode: 40500
-- v9fs_fid_create (31275): fid create fid 1
-- v9fs_fid_insert (31275): fid 1 (d7b88720) dentry new (c7ce3ef8)
-- v9fs_vfs_lookup (31275): dir: d2e45c18 dentry: (body) c91da388 nameidata: c7050f34
-- v9fs_fid_lookup (31275): dentry: new (c7ce3ef8)
-- v9fs_t_walk (31275): fid 1 newfid 2 wname 'body'
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 110
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 23
-- v9fs_write_work (31227): mux ddd39a00 sent 23 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 22 bytes
-- v9fs_deserialize_fcall (31227): size 22 id 111 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 111 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050e1c
-- v9fs_t_stat (31275): fid 2
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 124
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 11
-- v9fs_write_work (31227): mux ddd39a00 sent 11 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 86 bytes
-- v9fs_deserialize_fcall (31227): size 86 id 125 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 125 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050e20
-- v9fs_get_inode (31275): super block: df556400 mode: 100600
-- v9fs_fid_create (31275): fid create fid 2
-- v9fs_fid_insert (31275): fid 2 (c75815c0) dentry body (c91da388)
-- v9fs_fid_lookup (31275): dentry: body (c91da388)
-- v9fs_vfs_setattr (31275):
-- v9fs_t_wstat (31275): fid 2
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 126
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 62
-- v9fs_write_work (31227): mux ddd39a00 sent 62 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 26 bytes
-- v9fs_deserialize_fcall (31227): size 26 id 107 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 107 tag 0
-- process_request (31227): Rerror permission denied
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050d70
-- v9fs_vfs_setattr (31275): wstat error: permission denied
-- v9fs_dentry_delete (31275): dentry: body (c91da388)
-- v9fs_dentry_release (31275): dentry: body (c91da388)
-- v9fs_t_clunk (31275): fid 2
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 120
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 11
-- v9fs_write_work (31227): mux ddd39a00 sent 11 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 7 bytes
-- v9fs_deserialize_fcall (31227): size 7 id 121 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 121 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050e24
-- v9fs_dentry_delete (31275): dentry: new (c7ce3ef8)
-- v9fs_dentry_release (31275): dentry: new (c7ce3ef8)
-- v9fs_t_clunk (31275): fid 1
-- v9fs_send_request (31275): mux ddd39a00 task c5e1b200 tcall c4ce8600 id 120
-- v9fs_write_work (31227): mux ddd39a00 pos 0 size 11
-- v9fs_write_work (31227): mux ddd39a00 sent 11 bytes
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can read
-- v9fs_poll_mux (32005): schedule read work mux ddd39a00
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_read_work (31227): start mux ddd39a00 pos 0
-- v9fs_read_work (31227): mux ddd39a00 got 7 bytes
-- v9fs_deserialize_fcall (31227): size 7 id 121 tag 0
-- v9fs_read_work (31227): mux ddd39a00 fcall id 121 tag 0
-- v9fs_mux_rpc_cb (31227): req d13bea20 r c7050e24
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
-- v9fs_poll_mux (32005): mux ddd39a00 can write
-- v9fs_poll_proc (32005): sleeping...
[-- Attachment #1.3: Type: text/plain, Size: 188 bytes --]
Thanks for your patience,
Paul
On 20-Nov-06, at 4:27 PM, ron minnich wrote:
> mount it with debug=255 and look at the error. Or, did dmesg show
> anything at all?
>
> ron
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 193 bytes --]
next prev parent reply other threads:[~2006-11-21 1:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 19:06 Paul Lalonde
2006-11-20 19:15 ` erik quanstrom
2006-11-20 22:35 ` Paul Lalonde
2006-11-21 0:27 ` ron minnich
2006-11-21 1:16 ` Paul Lalonde [this message]
2006-11-21 2:36 ` ron minnich
2006-11-21 2:42 ` Paul Lalonde
2006-11-21 2:49 ` ron minnich
2006-11-21 3:00 ` erik quanstrom
2006-11-21 3:17 ` [9fans] read of eof Michael Baldwin
2006-11-21 6:38 ` Bruce Ellis
2006-11-21 1:23 ` [9fans] Re: echo -n arisawa
2006-11-21 2:32 ` ron minnich
2006-11-21 17:36 ` Andrew Lynch
2006-11-21 17:35 ` andrey mirtchovski
2006-11-21 18:13 ` Axel Belinfante
2006-11-21 18:23 ` andrey mirtchovski
2006-11-21 18:31 ` Axel Belinfante
2006-11-21 18:53 ` Skip Tavakkolian
2006-11-22 1:32 ` dmr
2006-11-24 4:17 ` Lyndon Nerenberg
2006-11-24 16:24 ` Bruce Ellis
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=F9AA6BA6-2D1E-4928-B285-9D90B0E85807@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).