[01:50:00] --- summatusmentis has left [02:07:41] --- lars.malinowsky has become available [02:40:01] --- Simon Wilkinson has left [04:18:35] --- jaltman/FrogsLeap has left: Disconnected [06:52:23] --- jaltman/FrogsLeap has become available [07:27:56] --- deason/gmail has become available [08:17:11] --- Simon Wilkinson has become available [08:17:41] --- summatusmentis has become available [08:24:31] --- lars.malinowsky has left [09:05:38] --- phalenor has left [09:05:40] --- phalenor has become available [11:22:52] --- reuteras has left [11:25:09] --- Simon Wilkinson has left [12:09:09] --- jakllsch/siwenna has left [12:09:10] --- jakllsch/wormulon has left [12:10:07] --- jakllsch/wormulon has become available [12:10:24] --- jakllsch/siwenna has become available [12:14:13] --- steven.jenkins has left [12:22:41] --- lars.malinowsky has become available [13:00:09] --- rra has become available [13:15:36] --- jaltman/FrogsLeap has left: Disconnected [13:55:15] --- matt has become available [13:56:27] Is anyone around with salvage/orphan dir experience? [13:57:06] I have apparently valid dumps which, when restored, blackhole the client. [13:58:23] "blackhole the client"; the volume looks empty? [13:59:59] More like: "ls: cannot access homer2: Connection timed out"--on other mounts, same viced, not so. [14:00:07] --- Simon has become available [14:00:27] I've forced-salvage (its dafs). And have various alerts. [14:01:14] FileLog doesn't say anything? [14:01:32] That's the SalvageLog. I have highest log level on viced, and -it- says -nothing- interesting. [14:02:06] it should at least log the op; what error code is it giving? [14:02:43] I'll restart... [14:05:16] and a dafs salvage would be logging to SalsrvLog [14:05:25] Yeah, and I have that output. [14:06:30] But honestly, it's like enumerating the directory containing the bad vols mount doesnt return. [14:07:06] The volume's id isn't in FileLog. [14:08:31] well, it might not be contacting the server still; fs flush/flushv/flushm? [14:08:39] was this volume moved? [14:08:48] or a different client [14:08:48] fs checkv might help as well [14:09:27] fs checkv reports all volumeIDname mappings checked. [14:09:47] fs checkv returns: Unknown error (64-bit unsigned overflow) [14:11:23] phalenor: The prototype of the volume is in service on a production fs--but I found an anomaly on it, so I've restored my last full dump. The new restored vol is the misbehaving vol. [14:12:29] The restore is actually in a dev cell. [14:13:08] > fs checkv reports > fs checkv returns: um... it does both? or... [14:13:29] oh, sorry. fs checkv reports all good. [14:13:35] fs flushv returned the overflow. [14:19:05] well, if you can get it to actually contact the fileserver I could probably tell you more about what's going on, whether that involves flushing or using another client or afscp or something [14:19:14] otherwise, the client seems confused, so we could look at that.... [14:24:06] You think it actually isn't contacting fs? [14:28:59] if viced at -d 125 doesn't log anything, it's not getting an error from viced [14:29:51] ah, I didn't really have it that high [14:30:49] well then you don't have the "highest log level" :) [14:31:15] you are correct, sir [14:31:25] if you don't wanna set it that high, I'd say look at volinfo output for the volume, or say what was in the log for the salvage [14:31:45] or dafssync-debug query [14:32:37] Its doing something bad when set that high. Like faulted. [14:34:55] er, then I'd want to know what specifically happened, if you get a core [14:35:41] yeah, I'll dig into things more carefully and let you know. It's a debug fileserver. [14:36:59] but I didn't mean to say that setting it that high is necessary; the other things I asked for are fine, too [14:40:39] It runs at 125. I had too many arguments. [14:45:02] http://pastebin.com/gqHPLsk8 [14:50:22] --- Simon has left [14:59:30] --- steven.jenkins has become available [16:19:16] --- deason/gmail has left [16:45:51] --- deason_gmail has become available [16:45:57] --- deason_gmail has left [16:46:40] --- deason/gmail has become available [16:49:22] (ftr, the problem was apparently a vldb entry pointed at localhost) [16:50:10] doh! [16:59:52] --- jakllsch has become available [17:00:09] --- jakllsch/siwenna has left [17:07:02] (yup. *sigh*) [17:23:26] --- matt has left [17:36:25] --- rra has left: Disconnected [20:21:44] --- Russ has become available [21:42:27] --- Russ has left: Disconnected [22:41:28] --- jaltman/FrogsLeap has become available [22:43:48] --- deason/gmail has left [22:45:53] --- jaltman/FrogsLeap has left: Replaced by new connection [22:45:53] --- jaltman/FrogsLeap has become available [22:48:11] --- jaltman/FrogsLeap has left: Replaced by new connection [22:48:11] --- jaltman/FrogsLeap has become available [22:53:15] --- jaltman/FrogsLeap has left: Replaced by new connection [22:53:15] --- jaltman/FrogsLeap has become available [23:08:08] --- lars.malinowsky has left [23:36:43] --- jaltman/FrogsLeap has left: Disconnected [23:36:51] --- jaltman/FrogsLeap has become available [23:38:43] --- jaltman/FrogsLeap has left: Disconnected [23:42:24] --- reuteras has become available [23:42:27] --- jaltman/FrogsLeap has become available [23:52:26] --- jaltman/FrogsLeap has left: Disconnected [23:54:06] --- jaltman/FrogsLeap has become available [23:55:40] --- lars.malinowsky has become available