search for: out_of_spac

Jeremy, I think we found the part of source where the problem resides: smbd/trans2.c +1444 for (i=0;(i<maxentries) && !finished && !out_of_space;i++) { +1445 BOOL got_exact_match = False; +1446 +1447 /* this is a heuristic to avoid seeking the dirptr except when +1448 absolutely necessary. It allows for a filename of about 40 chars */ +1449 if (space_remaining...

...at smbd/dir.c:565 #13 0x001c0be2 in get_lanman2_dir_entry (conn=0x91f7268, inbuf=0xb7d61008, outbuf=0xb7d40008, path_mask=0xbfebd120 "*", dirtype=22, info_level=260, requires_resume_key=4, dont_descend=0, ppdata=0xbfebd11c, base_data=0x91fa430 "`", space_remaining=14456, out_of_space=0xbfebd100, got_exact_match=0xbfebd07c, last_entry_off=0xbfebd118, name_list=0x0, ea_ctx=0x0) at smbd/trans2.c:1067 #14 0x001c3b9d in call_trans2findfirst (conn=0x91f7268, inbuf=0xb7d61008 "", outbuf=0xb7d40008 "", bufsize=131072, pparams=0xbfebda10, total_params=56, pp...

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them