[ceph-users] Re: Is there a way to find out which client uses which version of ceph?

[Wesley Dillingham]

You can ask the monitor to dump its sessions (which should expose the IPs
and the release / features) you can then track down by IP those with the
undesirable features/release

ceph daemon mon.`hostname -s` sessions

Assuming your mon is named after the short hostname, you may need to do
this for every mon.  Alternatively using the `ceph tell mon.* sessions` to
hit every mon at once.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Thu, Dec 21, 2023 at 10:46 AM Anthony D'Atri 
wrote:

> [rook@rook-ceph-tools-5ff8d58445-gkl5w .aws]$ ceph features
> {
> "mon": [
> {
> "features": "0x3f01cfbf7ffd",
> "release": "luminous",
> "num": 3
> }
> ],
> "osd": [
> {
> "features": "0x3f01cfbf7ffd",
> "release": "luminous",
> "num": 600
> }
> ],
> "client": [
> {
> "features": "0x2f018fb87aa4aafe",
> "release": "luminous",
> "num": 41
> },
> {
> "features": "0x3f01cfbf7ffd",
> "release": "luminous",
> "num": 147
> }
> ],
> "mgr": [
> {
> "features": "0x3f01cfbf7ffd",
> "release": "luminous",
> "num": 2
> }
> ]
> }
> [rook@rook-ceph-tools-5ff8d58445-gkl5w .aws]$
>
> IIRC there are nuances, there are case where a client can *look* like
> Jewel but actually be okay.
>
>
> > On Dec 21, 2023, at 10:41, Simon Oosthoek 
> wrote:
> >
> > Hi,
> >
> > Our cluster is currently running quincy, and I want to set the minimal
> > client version to luminous, to enable upmap balancer, but when I tried
> to,
> > I got this:
> >
> > # ceph osd set-require-min-compat-client luminous Error EPERM: cannot set
> > require_min_compat_client to luminous: 2 connected client(s) look like
> > jewel (missing 0x800); add --yes-i-really-mean-it to do it
> > anyway
> >
> > I think I know the most likely candidate (and I've asked them), but is
> > there a way to find out, the way ceph seems to know?
> >
> > tnx
> >
> > /Simon
> > --
> > I'm using my gmail.com address, because the gmail.com dmarc policy is
> > "none", some mail servers will reject this (microsoft?) others will
> instead
> > allow this when I send mail to a mailling list which has not yet been
> > configured to send mail "on behalf of" the sender, but rather do a kind
> of
> > "forward". The latter situation causes dkim/dmarc failures and the dmarc
> > policy will be applied. see https://wiki.list.org/DEV/DMARC for more
> details
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

maxrss using wrong unit in time

[Wesley Moore]

Hi folks,

Just thought I'd draw your attention to this bug since I think I've found the 
cause:
https://bugs.busybox.net/show_bug.cgi?id=15751

It seems that `time` is treating the the `ru_maxrss` value as a count of 
pages[1][2] but it's already in kilobytes[3]:

> ru_maxrss (since Linux 2.6.32)
> This is the maximum resident set size used (in kilobytes).

Regards,
Wes

[1]: https://git.busybox.net/busybox/tree/miscutils/time.c#n125
[2]: https://git.busybox.net/busybox/tree/miscutils/time.c#n284
[3]: https://man7.org/linux/man-pages/man2/getrusage.2.html
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

[ceph-users] Re: Logging control

[Wesley Dillingham]

"ceph daemon" commands need to be run local to the machine where the daemon
is running. So in this case if you arent on the node where osd.1 lives it
wouldnt work. "ceph tell" should work anywhere there is a client.admin key.


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, Dec 19, 2023 at 4:02 PM Tim Holloway  wrote:

> Ceph version is Pacific (16.2.14), upgraded from a sloppy Octopus.
>
> I ran afoul of all the best bugs in Octopus, and in the process
> switched on a lot of stuff better left alone, including some detailed
> debug logging. Now I can't turn it off.
>
> I am confidently informed by the documentation that the first step
> would be the command:
>
> ceph daemon osd.1 config show | less
>
> But instead of config information I get back:
>
> Can't get admin socket path: unable to get conf option admin_socket for
> osd: b"error parsing 'osd': expected string of the form TYPE.ID, valid
> types are: auth, mon, osd, mds, mgr, client\n"
>
> Which seems to be kind of insane.
>
> Attempting to get daemon config info on a monitor on that machine
> gives:
>
> admin_socket: exception getting command descriptions: [Errno 2] No such
> file or directory
>
> Which doesn't help either.
>
> Anyone got an idea?
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: [RBW] Re: Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

Hey Patrick,
Maybe you've already completed your two-speed conversion, but if not, there 
is some useful info in yesterday's Bikesnob 
blog: https://bikesnobnyc.com/2023/11/29/dingle-all-the-way/

The key message is that the Surly single-speed cogs are thicker at the base 
so you could use one for your second cog without needing a spacer. It 
should allow the lockring to fit.
-Wes

On Sunday, October 29, 2023 at 12:42:39 PM UTC-7 Patrick Moore wrote:

> Excellent! Thank you! So there is serendipity in that the lockring threads 
> match standard fw threads. Very good to know.
>
> Now I can simply overhaul that cheap ss freehub -- Redline? -- and don't 
> have to spend $$$ for a DOS; *also* I can use the current 32 t ring with 
> an outer, screw-on 15 t cog for a 65" cruising gear and buy a splined ss 17 
> or perhaps even 18 t cog for a 57" or even 54" sand bogging gear -- if, 
> that is, a QR disc rear wheel allows this.
>
> On Sun, Oct 29, 2023 at 9:49 AM Wesley  wrote:
>
>> Hi Patrick!
>> I don't remember the hub, and I searched my email for hubs I bought in 
>> 2009 – I was only able to find the one I built into the front wheel. 
>> However! This exercise show something loose in my head and I now recall how 
>> I made the monocog into a two-speed (before whatever I did to add a third 
>> cog). I replaced the locking by a fixed-gear cog. Here's a text diagram:
>>
>> Your current setup has: spokes - spacer - splined cog - lockring
>>
>> Change it to: spokes - splined cog - spacer - threaded cog
>>
>> I hope this helps!
>> -Wes
>>
>> On Saturday, October 28, 2023 at 9:51:46 PM UTC-7 Patrick Moore wrote:
>>
>>> Do you recall the hub you used with the unicycle rim? I seem to recall 
>>> BMX freehubs that had room for 2 cogs.
>>>
>>> On Sat, Oct 28, 2023 at 9:16 PM Wesley  wrote:
>>>
>>>> Yeah, it looks marginal to get a second cog in there with a narrower 
>>>> spacer. According to Sheldon Brown, 9-speed cogs want a 2.54 mm spacer 
>>>> between the cogs: https://sheldonbrown.com/cribsheet-spacing.html
>>>>
>>>> I now remember that my monocog became a three speed after I built it a 
>>>> pair of winter wheels (I used a pair of very wide unicycle rims for 
>>>> maximum 
>>>> float). So I probably kept the original when intact and built a new hub 
>>>> into the new wheel. Sorry for not remembering, the bike has been out of my 
>>>> life for about eight years.
>>>>
>>>> -W
>>>> On Saturday, October 28, 2023 at 1:17:17 PM UTC-7 Patrick Moore wrote:
>>>>
>>>>> Wesley: Sorry, I missed this post in the thread volume.
>>>>>
>>>>> I'm pretty sure that my Monocog's freehub body takes only 1 cog; see 
>>>>> photo with single 3/32" cog and 2.5mm spacer: the splines end right after 
>>>>> the spacer.
>>>>>
>>>>> Am I looking at things right? I hesitate to remove the wheel because 
>>>>> getting the tire exactly centered in the chainstays, with 2-3 mm 
>>>>> clearance 
>>>>> a side and the inevitable tire runout, while also adjusting chain tension 
>>>>> is a pain.
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>> On Tue, Oct 17, 2023 at 3:56 PM Wesley  wrote:
>>>>>
>>>>>> Hey Patrick,
>>>>>> My recollection of my monocog was that the freehub had room for three 
>>>>>> cogs. I think there were spacers on the hub that covered up most of the 
>>>>>> free hub - remove the locking and you can do adjust the spacers as 
>>>>>> necessary. If yours is the same, then you could just keep that wheel and 
>>>>>> put the additional cogs onto it.
>>>>>>
>>>>>> And, in case I wasn't clear in my earlier response, I think there is 
>>>>>> plenty of adjustment room in the disc brakes to accommodate the rear 
>>>>>> axle 
>>>>>> being adjusted in the dropout.
>>>>>> -Wes
>>>>>>
>>>>>> On Tuesday, October 17, 2023 at 10:44:19 AM UTC-7 Patrick Moore wrote:
>>>>>>
>>>>>>> That's interesting, and after blundering into a few search result 
>>>>>>> pages about money markets and currency conversion I got:
>>>>>>>
>>>>>>> http://www.monebikes.com/read-me/
>>>>>>>
>>>>>>

[ceph-users] Re: Best Practice for OSD Balancing

[Wesley Dillingham]

It's a complicated topic and there is no one answer, it varies for each
cluster and depends. You have a good lay of the land.

I just wanted to mention that the correct "foundation" for equally utilized
OSDs within a cluster relies on two important factors:

- Symmetry of disk/osd quantity and capacity (weight) between hosts.
- Achieving the correct amount of PGs-per-osd (typically between 100 and
200).

Without having reasonable settings/configurations for these two factors the
various higher-level balancing techniques wont work too well/at all.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, Nov 28, 2023 at 3:27 PM Rich Freeman  wrote:

> I'm fairly new to Ceph and running Rook on a fairly small cluster
> (half a dozen nodes, about 15 OSDs).  I notice that OSD space use can
> vary quite a bit - upwards of 10-20%.
>
> In the documentation I see multiple ways of managing this, but no
> guidance on what the "correct" or best way to go about this is.  As
> far as I can tell there is the balancer, manual manipulation of upmaps
> via the command line tools, and OSD reweight.  The last two can be
> optimized with tools to calculate appropriate corrections.  There is
> also the new read/active upmap (at least for non-EC pools), which is
> manually triggered.
>
> The balancer alone is leaving fairly wide deviations in space use, and
> at times during recovery this can become more significant.  I've seen
> OSDs hit the 80% threshold and start impacting IO when the entire
> cluster is only 50-60% full during recovery.
>
> I've started using ceph osd reweight-by-utilization and that seems
> much more effective at balancing things, but this seems redundant with
> the balancer which I have turned on.
>
> What is generally considered the best practice for OSD balancing?
>
> --
> Rich
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: OSDs failing to start due to crc32 and osdmap error

[Wesley Dillingham]

So those options are not consistent with the error in the video I linked.

I am not entirely sure how to proceed with your OSDs (how many are
impacted?)

but you may want to try injecting an older osdmap epoch fetched from the
mon in your osdmap injection:

try rewinding 1 epoch at a time from the current and see if that gets them
to start.

Proceed with caution, I would test this as well.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, Nov 27, 2023 at 2:36 PM Denis Polom  wrote:

> it's:
>
> "bluestore_compression_algorithm": "snappy"
>
> "bluestore_compression_mode": "none"
>
>
> On 11/27/23 20:13, Wesley Dillingham wrote:
>
> How about these two options:
>
> bluestore_compression_algorithm
> bluestore_compression_mode
>
> Thanks.
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Mon, Nov 27, 2023 at 2:01 PM Denis Polom  wrote:
>
>> Hi,
>>
>> no we don't:
>>
>> "bluestore_rocksdb_options":
>> "compression=kNoCompression,max_write_buffer_number=4,min_write_buffer_number_to_merge=1,recycle_log_file_num=4,write_buffer_size=268435456,writable_file_max_buffer_size=0,compaction_readahead_size=2097152,max_background_compactions=2,max_total_wal_size=1073741824",
>> thx
>>
>> On 11/27/23 19:17, Wesley Dillingham wrote:
>>
>> Curious if you are using bluestore compression?
>>
>> Respectfully,
>>
>> *Wes Dillingham*
>> w...@wesdillingham.com
>> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>>
>>
>> On Mon, Nov 27, 2023 at 10:09 AM Denis Polom 
>> wrote:
>>
>>> Hi
>>>
>>> we have issue to start some OSDs on one node on our Ceph Quincy 17.2.7
>>> cluster. Some OSDs on that node are running fine, but some failing to
>>> start.
>>>
>>> Looks like crc32 checksum error, and failing to get OSD map. I found a
>>> some discussions on that but nothing helped.
>>>
>>> I've also tried to insert current OSD map but that ends with error:
>>>
>>> # CEPH_ARGS="--bluestore-ignore-data-csum" ceph-objectstore-tool
>>> --data-path /var/lib/ceph/osd/ceph-888/ --op set-osdmap --file osdmap
>>> osdmap (#-1:20684533:::osdmap.931991:0#) does not exist.
>>>
>>> Log is bellow
>>>
>>> Any ideas please?
>>>
>>> Thank you
>>>
>>>
>>>  From log file:
>>>
>>> 2023-11-27T16:01:47.691+0100 7f3f17aa13c0 -1 Falling back to public
>>> interface
>>>
>>> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1
>>> bluestore(/var/lib/ceph/osd/ceph-888) _verify_csum bad crc32c/0x1000
>>> checksum at blob offset 0x0, got 0xb1701b42, expected 0x9ee5ece2, device
>>> location [0x1~1000], logical extent 0x0~1000, object
>>> #-1:7b3f43c4:::osd_superblock:0#
>>>
>>> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1 osd.888 0 failed to load
>>> OSD map for epoch 927580, got 0 bytes
>>>
>>> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
>>> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
>>> 2023-11-27T16:01:51.443522+0100
>>> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>>> (stable)
>>>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>>> const*)+0x14f) [0x561ad07d2624]
>>>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>>>   4: main()
>>>   5: __libc_start_main()
>>>   6: _start()
>>> *** Caught signal (Aborted) **
>>>   in thread 7f3f17aa13c0 thread_name:ceph-osd
>>> 2023-11-27T16:01:51.443+0100 7f3f17aa13c0 -1
>>> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
>>> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
>>> 2023-11-27T16:01:51.443522+0100
>>> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>>>
>>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>>> (stable)
>>>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>>> const*)+0x14f) [0x561ad07d2624]
>>>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>>>   4: main()
>>>   5: __libc_start_main()
>>>   

[ceph-users] Re: OSDs failing to start due to crc32 and osdmap error

[Wesley Dillingham]

What I was getting at was to see if this was somehow related to the bug
described here https://www.youtube.com/watch?v=_4HUR00oCGo

It should not be given the version of ceph you are using but the CRC error
you are seeing is similar.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, Nov 27, 2023 at 2:19 PM Anthony D'Atri  wrote:

> The options Wes listed are for data, not RocksDB.
>
> > On Nov 27, 2023, at 1:59 PM, Denis Polom  wrote:
> >
> > Hi,
> >
> > no we don't:
> >
> > "bluestore_rocksdb_options":
> "compression=kNoCompression,max_write_buffer_number=4,min_write_buffer_number_to_merge=1,recycle_log_file_num=4,write_buffer_size=268435456,writable_file_max_buffer_size=0,compaction_readahead_size=2097152,max_background_compactions=2,max_total_wal_size=1073741824",
> >
> > thx
> >
> > On 11/27/23 19:17, Wesley Dillingham wrote:
> >> Curious if you are using bluestore compression?
> >>
> >> Respectfully,
> >>
> >> *Wes Dillingham*
> >> w...@wesdillingham.com
> >> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
> >>
> >>
> >> On Mon, Nov 27, 2023 at 10:09 AM Denis Polom 
> wrote:
> >>
> >>Hi
> >>
> >>we have issue to start some OSDs on one node on our Ceph Quincy
> >>17.2.7
> >>cluster. Some OSDs on that node are running fine, but some failing
> >>to start.
> >>
> >>Looks like crc32 checksum error, and failing to get OSD map. I
> >>found a
> >>some discussions on that but nothing helped.
> >>
> >>I've also tried to insert current OSD map but that ends with error:
> >>
> >># CEPH_ARGS="--bluestore-ignore-data-csum" ceph-objectstore-tool
> >>--data-path /var/lib/ceph/osd/ceph-888/ --op set-osdmap --file osdmap
> >>osdmap (#-1:20684533:::osdmap.931991:0#) does not exist.
> >>
> >>Log is bellow
> >>
> >>Any ideas please?
> >>
> >>Thank you
> >>
> >>
> >> From log file:
> >>
> >>2023-11-27T16:01:47.691+0100 7f3f17aa13c0 -1 Falling back to public
> >>interface
> >>
> >>2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1
> >>bluestore(/var/lib/ceph/osd/ceph-888) _verify_csum bad crc32c/0x1000
> >>checksum at blob offset 0x0, got 0xb1701b42, expected 0x9ee5ece2,
> >>device
> >>location [0x1~1000], logical extent 0x0~1000, object
> >>#-1:7b3f43c4:::osd_superblock:0#
> >>
> >>2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1 osd.888 0 failed to load
> >>OSD map for epoch 927580, got 0 bytes
> >>
> >>/build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
> >>OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
> >>2023-11-27T16:01:51.443522+0100
> >>/build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
> >>  ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2)
> >>quincy
> >>(stable)
> >>  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> >>const*)+0x14f) [0x561ad07d2624]
> >>  2: ceph-osd(+0xc2e836) [0x561ad07d2836]
> >>  3: (OSD::init()+0x4026) [0x561ad08e5a86]
> >>  4: main()
> >>  5: __libc_start_main()
> >>  6: _start()
> >>*** Caught signal (Aborted) **
> >>  in thread 7f3f17aa13c0 thread_name:ceph-osd
> >>2023-11-27T16:01:51.443+0100 7f3f17aa13c0 -1
> >>/build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
> >>OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
> >>2023-11-27T16:01:51.443522+0100
> >>/build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
> >>
> >>  ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2)
> >>quincy
> >>(stable)
> >>  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> >>const*)+0x14f) [0x561ad07d2624]
> >>  2: ceph-osd(+0xc2e836) [0x561ad07d2836]
> >>  3: (OSD::init()+0x4026) [0x561ad08e5a86]
> >>  4: main()
> >>  5: __libc_start_main()
> >>  6: _start()
> >>
> >>
> >>  ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2)
> >>quincy
> >>(stable)
> >>  1: /lib/x86_64-linux-gnu/libpthr

[ceph-users] Re: OSDs failing to start due to crc32 and osdmap error

[Wesley Dillingham]

How about these two options:

bluestore_compression_algorithm
bluestore_compression_mode

Thanks.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, Nov 27, 2023 at 2:01 PM Denis Polom  wrote:

> Hi,
>
> no we don't:
>
> "bluestore_rocksdb_options":
> "compression=kNoCompression,max_write_buffer_number=4,min_write_buffer_number_to_merge=1,recycle_log_file_num=4,write_buffer_size=268435456,writable_file_max_buffer_size=0,compaction_readahead_size=2097152,max_background_compactions=2,max_total_wal_size=1073741824",
> thx
>
> On 11/27/23 19:17, Wesley Dillingham wrote:
>
> Curious if you are using bluestore compression?
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Mon, Nov 27, 2023 at 10:09 AM Denis Polom  wrote:
>
>> Hi
>>
>> we have issue to start some OSDs on one node on our Ceph Quincy 17.2.7
>> cluster. Some OSDs on that node are running fine, but some failing to
>> start.
>>
>> Looks like crc32 checksum error, and failing to get OSD map. I found a
>> some discussions on that but nothing helped.
>>
>> I've also tried to insert current OSD map but that ends with error:
>>
>> # CEPH_ARGS="--bluestore-ignore-data-csum" ceph-objectstore-tool
>> --data-path /var/lib/ceph/osd/ceph-888/ --op set-osdmap --file osdmap
>> osdmap (#-1:20684533:::osdmap.931991:0#) does not exist.
>>
>> Log is bellow
>>
>> Any ideas please?
>>
>> Thank you
>>
>>
>>  From log file:
>>
>> 2023-11-27T16:01:47.691+0100 7f3f17aa13c0 -1 Falling back to public
>> interface
>>
>> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1
>> bluestore(/var/lib/ceph/osd/ceph-888) _verify_csum bad crc32c/0x1000
>> checksum at blob offset 0x0, got 0xb1701b42, expected 0x9ee5ece2, device
>> location [0x1~1000], logical extent 0x0~1000, object
>> #-1:7b3f43c4:::osd_superblock:0#
>>
>> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1 osd.888 0 failed to load
>> OSD map for epoch 927580, got 0 bytes
>>
>> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
>> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
>> 2023-11-27T16:01:51.443522+0100
>> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>> (stable)
>>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>> const*)+0x14f) [0x561ad07d2624]
>>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>>   4: main()
>>   5: __libc_start_main()
>>   6: _start()
>> *** Caught signal (Aborted) **
>>   in thread 7f3f17aa13c0 thread_name:ceph-osd
>> 2023-11-27T16:01:51.443+0100 7f3f17aa13c0 -1
>> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
>> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
>> 2023-11-27T16:01:51.443522+0100
>> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>>
>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>> (stable)
>>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>> const*)+0x14f) [0x561ad07d2624]
>>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>>   4: main()
>>   5: __libc_start_main()
>>   6: _start()
>>
>>
>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>> (stable)
>>   1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f3f1814b420]
>>   2: gsignal()
>>   3: abort()
>>   4: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>> const*)+0x1b7) [0x561ad07d268c]
>>   5: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>   6: (OSD::init()+0x4026) [0x561ad08e5a86]
>>   7: main()
>>   8: __libc_start_main()
>>   9: _start()
>> 2023-11-27T16:01:51.447+0100 7f3f17aa13c0 -1 *** Caught signal (Aborted)
>> **
>>   in thread 7f3f17aa13c0 thread_name:ceph-osd
>>
>>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
>> (stable)
>>   1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f3f1814b420]
>>   2: gsignal()
>>   3: abort()
>>   4: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>> const*)+0x1b7) [0x561ad07d268c]
>>   5: ceph-osd(+0xc2e836) [0x561ad07d2836]
>>   6: (OSD::init()+0x4026) [0x561ad08e5a86]
>>   7: main()
>>   8: __libc_start_main()
&g

[ceph-users] Re: About number of osd node can be failed with erasure code 3+2

[Wesley Dillingham]

With a k+m which is 3+2 each RADOS object is broken into 5 shards. By
default the pool will have a min_size of k+1 (4 in this case). Which means
you can lose 1 shard and still be >= min_size. If one host goes down and
you use a host-based failure domain (default) you will lose 1 shard out of
all PGs on that host. You will now be at min_size and so still
readable/writeable. If you lose another host you will now be below min_size
with 3 healthy shards for some subset of PG (those common to the 2 hosts)
will be inactive and therefore not read/writeable. As you can see, the
higher your M the more disks/hosts you can lose before dropping below
min_size.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Nov 27, 2023 at 1:36 PM  wrote:

> Hi Groups,
>
> Recently I was setting up a ceph cluster with 10 nodes 144 osd, and I use
> S3 for it with pool erasure code EC3+2 on it.
>
> I have a question, how many osd nodes can fail with erasure code 3+2 with
> cluster working normal (read, write)? and can i choose better erasure code
> ec7+3, 8+2 etc..?
>
> With the erasure code algorithm, it only ensures no data loss, but does
> not guarantee that the cluster operates normally and does not block IO when
> osd nodes down. Is that right?
>
> Thanks to the community.
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: OSDs failing to start due to crc32 and osdmap error

[Wesley Dillingham]

Curious if you are using bluestore compression?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Nov 27, 2023 at 10:09 AM Denis Polom  wrote:

> Hi
>
> we have issue to start some OSDs on one node on our Ceph Quincy 17.2.7
> cluster. Some OSDs on that node are running fine, but some failing to
> start.
>
> Looks like crc32 checksum error, and failing to get OSD map. I found a
> some discussions on that but nothing helped.
>
> I've also tried to insert current OSD map but that ends with error:
>
> # CEPH_ARGS="--bluestore-ignore-data-csum" ceph-objectstore-tool
> --data-path /var/lib/ceph/osd/ceph-888/ --op set-osdmap --file osdmap
> osdmap (#-1:20684533:::osdmap.931991:0#) does not exist.
>
> Log is bellow
>
> Any ideas please?
>
> Thank you
>
>
>  From log file:
>
> 2023-11-27T16:01:47.691+0100 7f3f17aa13c0 -1 Falling back to public
> interface
>
> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1
> bluestore(/var/lib/ceph/osd/ceph-888) _verify_csum bad crc32c/0x1000
> checksum at blob offset 0x0, got 0xb1701b42, expected 0x9ee5ece2, device
> location [0x1~1000], logical extent 0x0~1000, object
> #-1:7b3f43c4:::osd_superblock:0#
>
> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1 osd.888 0 failed to load
> OSD map for epoch 927580, got 0 bytes
>
> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
> 2023-11-27T16:01:51.443522+0100
> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
> (stable)
>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x14f) [0x561ad07d2624]
>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>   4: main()
>   5: __libc_start_main()
>   6: _start()
> *** Caught signal (Aborted) **
>   in thread 7f3f17aa13c0 thread_name:ceph-osd
> 2023-11-27T16:01:51.443+0100 7f3f17aa13c0 -1
> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
> 2023-11-27T16:01:51.443522+0100
> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
> (stable)
>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x14f) [0x561ad07d2624]
>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>   4: main()
>   5: __libc_start_main()
>   6: _start()
>
>
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
> (stable)
>   1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f3f1814b420]
>   2: gsignal()
>   3: abort()
>   4: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x1b7) [0x561ad07d268c]
>   5: ceph-osd(+0xc2e836) [0x561ad07d2836]
>   6: (OSD::init()+0x4026) [0x561ad08e5a86]
>   7: main()
>   8: __libc_start_main()
>   9: _start()
> 2023-11-27T16:01:51.447+0100 7f3f17aa13c0 -1 *** Caught signal (Aborted) **
>   in thread 7f3f17aa13c0 thread_name:ceph-osd
>
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
> (stable)
>   1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f3f1814b420]
>   2: gsignal()
>   3: abort()
>   4: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x1b7) [0x561ad07d268c]
>   5: ceph-osd(+0xc2e836) [0x561ad07d2836]
>   6: (OSD::init()+0x4026) [0x561ad08e5a86]
>   7: main()
>   8: __libc_start_main()
>   9: _start()
>   NOTE: a copy of the executable, or `objdump -rdS ` is
> needed to interpret this.
>
>
>-558> 2023-11-27T16:01:47.691+0100 7f3f17aa13c0 -1 Falling back to
> public interface
>
>  -5> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1
> bluestore(/var/lib/ceph/osd/ceph-888) _verify_csum bad crc32c/0x1000
> checksum at blob offset 0x0, got 0xb1701b42, expected 0x9ee5ece2, device
> location [0x1~1000], logical extent 0x0~1000, object
> #-1:7b3f43c4:::osd_superblock:0#
>
>  -2> 2023-11-27T16:01:51.439+0100 7f3f17aa13c0 -1 osd.888 0 failed
> to load OSD map for epoch 927580, got 0 bytes
>
>  -1> 2023-11-27T16:01:51.443+0100 7f3f17aa13c0 -1
> /build/ceph-17.2.7/src/osd/OSD.h: In function 'OSDMapRef
> OSDService::get_map(epoch_t)' thread 7f3f17aa13c0 time
> 2023-11-27T16:01:51.443522+0100
> /build/ceph-17.2.7/src/osd/OSD.h: 696: FAILED ceph_assert(ret)
>
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy
> (stable)
>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x14f) [0x561ad07d2624]
>   2: ceph-osd(+0xc2e836) [0x561ad07d2836]
>   3: (OSD::init()+0x4026) [0x561ad08e5a86]
>   4: main()
>   5: __libc_start_main()
>   6: _start()
>
>
>   0> 2023-11-27T16:01:51.447+0100 7f3f17aa13c0 -1 *** Caught signal
> (Aborted) **
>   in thread 7f3f17aa13c0 thread_name:ceph-osd
>
>   ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy

Basic Access for Google Ads API

[Wesley Ferreira]

Hi, 

I've been filling out the form to request basic access for weeks, but I 
haven't received a response. I contacted the Ads API Compliance team, but I 
haven't received a response yet.
We are not getting any feedback from you from any location.
We are developing software for publishing campaigns on Google Ads for large 
retailers.
Can you help me!?

MCC 241-355-4854
Access level: Basic Access

Thanks.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a01514cf-4ae5-492d-a593-6038f364b61bn%40googlegroups.com.

[ceph-users] Re: Why is min_size of erasure pools set to k+1

[Wesley Dillingham]

" if min_size is k and you lose an OSD during recovery after a failure of m
OSDs, data will become unavailable"

In that situation data wouldnt become unavailable it would be lost.

Having a min_size of k+1 provides a buffer between data being
active+writeable and where data is lost. That inbetween is called inactive.

By having that buffer you prevent the situation of having data being
written to the PG when you are only one disk/shard away from data loss.

Imagine the scenario of 4+2 with a min_size of 4. The cluster is 6 servers
filled with osds

You have brought 2 servers down for maintenance (not a good idea but this
is an example). Your PGs are all degraded with only 4 shards of clean data
but active because k=min_size. Data is being written to the pool.

As you are booting your 2 servers up out of maintenance an OSD/disk on
another server fails and fails hard. Because that OSD was part of the
acting set the cluster only wrote four shards and now one is lost.

You only have 3 shards of data in a 4+2 and now some subset of data is lost.

Now imagine a 4+2 with min_size = 5.

You wouldnt bring down more than 1 host because "ceph osd ok-to-stop" would
return false if your tried to bring down more than 1 host for maintenance.

Lets say you did bring down two hosts against the advice of the ok-to-stop
command your PGs would become inactive and so they wouldn't accept
writes. Once you boot your 2 servers back the cluster heals.

Lets say you heed the advice of ok-to-stop and only bring 1 host down for
maintenance at a time.  Your data is degraded with 5/6 shards healthy. New
data is being written with 5 shards able to be written out.

As you are booting your server out of maintenance an OSD on another host
dies and those shards are lost forever, The PGs from that lost OSD now have
4  healthy shards. That is enough shards to recover the data from (though
you would have some PGs inactive for a bit until recovery finished)

Hope this helps to answer the min_size question a bit.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Nov 20, 2023 at 2:03 PM Vladimir Brik <
vladimir.b...@icecube.wisc.edu> wrote:

> Could someone help me understand why it's a bad idea to set min_size of
> erasure-coded pools to k?
>
> From what I've read, the argument for k+1 is that if min_size is k and you
> lose an OSD during recovery after a failure of m OSDs, data will become
> unavailable. But how does setting min_size to k+1 help? If m=2, if you
> experience a double failure followed by another failure during recovery you
> still lost 3 OSDs and therefore your data because the pool wasn't set up to
> handle 3 concurrent failures, and the value of min_size is irrelevant.
>
> https://github.com/ceph/ceph/pull/8008 mentions inability to peer if
> min_size = k, but I don't understand why. Does that mean that if min_size=k
> and I lose m OSDs, and then an OSD is restarted during recovery, PGs will
> not peer even after the restarted OSD comes back online?
>
>
> Vlad
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: blustore osd nearfull but no pgs on it

[Wesley Dillingham]

The large amount of osdmaps is what i was suspecting. "ceph tell osd.158
status" (or any osd other than 158) would show us how many osdmaps the osds
are currently holding on to.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, Nov 20, 2023 at 6:15 AM Debian  wrote:

> Hi,
>
> yes all of my small osds are affected
>
> i found the issue, my cluster is healthy and my rebalance finished - i
> have only to wait that my old osdmaps get cleaned up.
>
> like in the thread "Disks are filling up even if there is not a single
> placement group on them"
>
> thx!
>
> On 20.11.23 11:36, Eugen Block wrote:
> > You provide only a few details at a time, it would help to get a full
> > picture if you provided the output Wesley asked for (ceph df detail,
> > ceph tell osd.158 status, ceph osd df tree). Is osd.149 now the
> > problematic one or did you just add output from a different osd?
> > It's not really clear what you're doing without the necessary context.
> > You can just add the 'ceph daemon osd.{OSD} perf dump' output here or
> > in some pastebin.
> >
> > Zitat von Debian :
> >
> >> Hi,
> >>
> >> the block.db size ist default and not custom configured:
> >>
> >> current:
> >>
> >> bluefs.db_used_bytes: 9602859008
> >> bluefs.db_used_bytes: 469434368
> >>
> >> ceph daemon osd.149 config show
> >>
> >> "bluestore_bitmapallocator_span_size": "1024",
> >> "bluestore_block_db_size": "0",
> >> "bluestore_block_size": "107374182400",
> >> "bluestore_block_wal_size": "100663296",
> >> "bluestore_cache_size": "0",
> >> "bluestore_cache_size_hdd": "1073741824",
> >> "bluestore_cache_size_ssd": "3221225472",
> >> "bluestore_compression_max_blob_size": "0",
> >> "bluestore_compression_max_blob_size_hdd": "524288",
> >> "bluestore_compression_max_blob_size_ssd": "65536",
> >> "bluestore_compression_min_blob_size": "0",
> >> "bluestore_compression_min_blob_size_hdd": "131072",
> >> "bluestore_compression_min_blob_size_ssd": "8192",
> >> "bluestore_extent_map_inline_shard_prealloc_size": "256",
> >> "bluestore_extent_map_shard_max_size": "1200",
> >> "bluestore_extent_map_shard_min_size": "150",
> >> "bluestore_extent_map_shard_target_size": "500",
> >> "bluestore_extent_map_shard_target_size_slop": "0.20",
> >> "bluestore_max_alloc_size": "0",
> >> "bluestore_max_blob_size": "0",
> >> "bluestore_max_blob_size_hdd": "524288",
> >> "bluestore_max_blob_size_ssd": "65536",
> >> "bluestore_min_alloc_size": "0",
> >> "bluestore_min_alloc_size_hdd": "65536",
> >> "bluestore_min_alloc_size_ssd": "4096",
> >> "bluestore_prefer_deferred_size": "0",
> >> "bluestore_prefer_deferred_size_hdd": "32768",
> >> "bluestore_prefer_deferred_size_ssd": "0",
> >> "bluestore_rocksdb_options":
> >>
> "compression=kNoCompression,max_write_buffer_number=4,min_write_buffer_number_to_merge=1,recycle_log_file_num=4,write_buffer_size=268435456,writable_file_max_buffer_size=0,compaction_readahead_size=2097152,max_background_compactions=2",
> >>
> >> "bluefs_alloc_size": "1048576",
> >> "bluefs_allocator": "hybrid",
> >> "bluefs_buffered_io": "false",
> >> "bluefs_check_for_zeros": "false",
> >> "bluefs_compact_log_sync": "false",
> >> "bluefs_log_compact_min_ratio": "5.00",
> >> "bluefs_log_compact_min_size": "16777216",
> >> "bluefs_max_log_runway": "4194304",
> >> "bluefs_max_prefetch": "1048576",
> >> "bluefs_min_flush_size": "524288",
> >> "bluefs_min_log_r

Re: Perl Design Patterns

[wesley]

you can choose to not use it.


> 
> When must I use perl design patterns?
> -- 
> 
> With kindest regards, William.
> 
> ⢀⣴⠾⠻⢶⣦⠀ 
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org https://www.debian.org/ 
> ⠈⠳⣄
>

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

[ceph-users] Re: blustore osd nearfull but no pgs on it

[Wesley Dillingham]

Please send along a pastebin of "ceph status" and "ceph osd df tree" and
"ceph df detail" also "ceph tell osd.158 status"

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Fri, Nov 17, 2023 at 6:20 PM Debian  wrote:

> thx for your reply, it shows nothing,... there are no pgs on the osd,...
>
> best regards
>
> On 17.11.23 23:09, Eugen Block wrote:
> > After you create the OSD, run ‚ceph pg ls-by-osd {OSD}‘, it should
> > show you which PGs are created there and then you’ll know which pool
> > they belong to, then check again the crush rule for that pool. You can
> > paste the outputs here.
> >
> > Zitat von Debian :
> >
> >> Hi,
> >>
> >> after a massive rebalance(tunables) my small SSD-OSDs are getting
> >> full, i changed my crush rules so there are actual no pgs/pools on
> >> it, but the disks stay full:
> >>
> >> ceph version 14.2.21 (5ef401921d7a88aea18ec7558f7f9374ebd8f5a6)
> >> nautilus (stable)
> >>
> >> ID CLASS WEIGHT REWEIGHT SIZERAW USE DATAOMAP
> >> META AVAIL%USE  VAR  PGS STATUS TYPE NAME
> >> 158   ssd0.21999  1.0 224 GiB 194 GiB 193 GiB  22 MiB 1002
> >> MiB   30 GiB 86.68 1.49   0 up osd.158
> >>
> >> inferring bluefs devices from bluestore path
> >> 1 : device size 0x37e440 : own 0x[1ad3f0~23c60] =
> >> 0x23c60 : using 0x3963(918 MiB) : bluestore has
> >> 0x46e2d(18 GiB) available
> >>
> >> when i recreate the osd the osd gets full again
> >>
> >> any suggestion?
> >>
> >> thx & best regards
> >> ___
> >> ceph-users mailing list -- ceph-users@ceph.io
> >> To unsubscribe send an email to ceph-users-le...@ceph.io
> >
> >
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: Anna Purple

[Wesley]

Purple is the best color, and this is a great purple. I love it.
-W

On Friday, November 17, 2023 at 6:34:41 AM UTC-8 Tim Bantham wrote:

> Curious what folks think of the Riv frames in purple. I personally am on 
> the fence. I keep looking at it and can't decide if I would like it or not. 
> I would be perfectly fine with any of the other Riv colors but the purple 
> is a bit polarizing to me. Of course I am betting it looks great in person. 
> Thoughts? 
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/07473ebf-3ac2-4138-b472-906c177b3ec2n%40googlegroups.com.

[ceph-users] Re: per-rbd snapshot limitation

[Wesley Dillingham]

Are you aware of any config item that can be set (perhaps in the ceph.conf
or config db) so the limit is enforced immediately at creation time without
needing to set it for each rbd?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Nov 15, 2023 at 1:14 PM David C.  wrote:

> rbd create testpool/test3 --size=100M
> rbd snap limit set testpool/test3 --limit 3
>
>
> Le mer. 15 nov. 2023 à 17:58, Wesley Dillingham  a
> écrit :
>
>> looking into how to limit snapshots at the ceph level for RBD snapshots.
>> Ideally ceph would enforce an arbitrary number of snapshots allowable per
>> rbd.
>>
>> Reading the man page for rbd command I see this option:
>> https://docs.ceph.com/en/quincy/man/8/rbd/#cmdoption-rbd-limit
>>
>> --limit
>>
>> Specifies the limit for the number of snapshots permitted.
>>
>> Seems perfect. But on attempting to use it as such I get an error:
>>
>> admin@rbdtest:~$ rbd create testpool/test3 --size=100M --limit=3
>> rbd: unrecognised option '--limit=3'
>>
>> Where am I going wrong here? Is there another way to enforce a limit of
>> snapshots for RBD? Thanks.
>>
>> Respectfully,
>>
>> *Wes Dillingham*
>> w...@wesdillingham.com
>> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: per-rbd snapshot limitation

[Wesley Dillingham]

Perfect, thank you.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Nov 15, 2023 at 1:00 PM Ilya Dryomov  wrote:

> On Wed, Nov 15, 2023 at 5:57 PM Wesley Dillingham 
> wrote:
> >
> > looking into how to limit snapshots at the ceph level for RBD snapshots.
> > Ideally ceph would enforce an arbitrary number of snapshots allowable per
> > rbd.
> >
> > Reading the man page for rbd command I see this option:
> > https://docs.ceph.com/en/quincy/man/8/rbd/#cmdoption-rbd-limit
> >
> > --limit
> >
> > Specifies the limit for the number of snapshots permitted.
> >
> > Seems perfect. But on attempting to use it as such I get an error:
> >
> > admin@rbdtest:~$ rbd create testpool/test3 --size=100M --limit=3
> > rbd: unrecognised option '--limit=3'
> >
> > Where am I going wrong here? Is there another way to enforce a limit of
> > snapshots for RBD? Thanks.
>
> Hi Wes,
>
> I think you want "rbd snap limit set --limit 3 testpool/test3".
>
> Thanks,
>
> Ilya
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] per-rbd snapshot limitation

[Wesley Dillingham]

looking into how to limit snapshots at the ceph level for RBD snapshots.
Ideally ceph would enforce an arbitrary number of snapshots allowable per
rbd.

Reading the man page for rbd command I see this option:
https://docs.ceph.com/en/quincy/man/8/rbd/#cmdoption-rbd-limit

--limit

Specifies the limit for the number of snapshots permitted.

Seems perfect. But on attempting to use it as such I get an error:

admin@rbdtest:~$ rbd create testpool/test3 --size=100M --limit=3
rbd: unrecognised option '--limit=3'

Where am I going wrong here? Is there another way to enforce a limit of
snapshots for RBD? Thanks.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: Hillborne fork on a Heron?

[Wesley]

Just FYI, you have more choices than you might think with the fork. If you 
find a fork you like but the steerer is too long, you can still use it!

If the upper race can't thread all the way down to the cup, you can swap 
your headset for a 1" threadless headset, and screw the top nut not the 
fork threads to provide preload to the headset without having to use the 
typical internal nut of a treadless headset. This means you can still use a 
quill stem with a threadless headset! I did this recently with a threaded 
fork having a vry long steerer in order to get my handlebars higher. 
Happy to provide ics later if that would be helpful.
-Wes

On Wednesday, November 8, 2023 at 12:22:21 PM UTC-8 h...@chrisdedinsky.com 
wrote:

> This week I was commuting home from work on my Heron. I got a flat on my 
> Challenge Strada Bianca 36 tires and on a whim—certainly inspired by the 
> recent 'Rondini' episode of Ron's bikes YouTube episode—decided to stuff in 
> a pair of much too large 700x42 Hurricane Ridge tires to enjoy until the 
> snow falls. Which should be pretty quick here in British Columbia's 
> southern interior.
>
> The fork clearance is decidedly too tight and perhaps irresponsible, if 
> not dangerous. I'm gonna keep my fenders on as I'm not sure how long this 
> experiment will last. So far a couple of sporting trips back and forth to 
> work. 
>
> It has got me thinking though, has anyone out there modified their Heron 
> to have more modern Riv tire clearances? In the vein of a Sam Hillborne. I 
> was daydreaming about putting a more tolerable fork and crimping the 
> chainstays, so I could run up in the +45 range. Although the rear wheel has 
> much more than a few sheets of paper in clearance and the irrevesability of 
> crimping makes me nervous. 
>
> Would love to hear any thoughts on the pro's/con's. And if there are any 
> extra hillborne forks out there for a ~57 frame, I may be interested. If 
> so, I can give specs. I know I should leave a perfectly wonderful frameset 
> alone, but I can't help but wonder about it. 
>
> Here are some pics that make the fit seem even more dramatic on that front 
> fork. 
>
> [image: IMG_4368.jpg]
> [image: IMG_4363.jpg]
> [image: IMG_4364.jpg]
> [image: IMG_4365.jpg]
> [image: IMG_4366.jpg]
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/90bb2a44-71d0-49c2-b451-90bfe783ed58n%40googlegroups.com.

[ceph-users] Re: owner locked out of bucket via bucket policy

[Wesley Dillingham]

Jaynath:

Just to be clear with the "--admin" user's key's you have attempted to
delete the bucket policy using the following method:
https://docs.aws.amazon.com/cli/latest/reference/s3api/delete-bucket-policy.html

This is what worked for me (on a 16.2.14 cluster). I didn't attempt to
interact with the affected bucket in any way other than "aws s3api
delete-bucket-policy"

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Nov 8, 2023 at 8:30 AM Jayanth Reddy 
wrote:

> Hello Casey,
>
> We're totally stuck at this point and none of the options seem to work.
> Please let us know if there is something in metadata or index to remove
> those applied bucket policies. We downgraded to v17.2.6 and encountering
> the same.
>
> Regards,
> Jayanth
>
> On Wed, Nov 8, 2023 at 7:14 AM Jayanth Reddy 
> wrote:
>
>> Hello Casey,
>>
>> And on further inspection, we identified that there were bucket policies
>> set from the initial days; we were in v16.2.12.
>> We upgraded the cluster to v17.2.7 two days ago and it seems obvious that
>> the IAM error logs are generated the next minute rgw daemon upgraded from
>> v16.2.12 to v17.2.7. Looks like there is some issue with parsing.
>>
>> I'm thinking to downgrade back to v17.2.6 and earlier, please let me know
>> if this is a good option for now.
>>
>> Thanks,
>> Jayanth
>> --
>> *From:* Jayanth Reddy 
>> *Sent:* Tuesday, November 7, 2023 11:59:38 PM
>> *To:* Casey Bodley 
>> *Cc:* Wesley Dillingham ; ceph-users <
>> ceph-users@ceph.io>; Adam Emerson 
>> *Subject:* Re: [ceph-users] Re: owner locked out of bucket via bucket
>> policy
>>
>> Hello Casey,
>>
>> Thank you for the quick response. I see
>> `rgw_policy_reject_invalid_principals` is not present in v17.2.7. Please
>> let me know.
>>
>> Regards
>> Jayanth
>>
>> On Tue, Nov 7, 2023 at 11:50 PM Casey Bodley  wrote:
>>
>> On Tue, Nov 7, 2023 at 12:41 PM Jayanth Reddy
>>  wrote:
>> >
>> > Hello Wesley and Casey,
>> >
>> > We've ended up with the same issue and here it appears that even the
>> user with "--admin" isn't able to do anything. We're now unable to figure
>> out if it is due to bucket policies, ACLs or IAM of some sort. I'm seeing
>> these IAM errors in the logs
>> >
>> > ```
>> >
>> > Nov  7 00:02:00 ceph-05 radosgw[4054570]: req 8786689665323103851
>> 0.00368s s3:get_obj Error reading IAM Policy: Terminate parsing due to
>> Handler error.
>> >
>> > Nov  7 22:51:40 ceph-05 radosgw[4054570]: req 13293029267332025583
>> 0.0s s3:list_bucket Error reading IAM Policy: Terminate parsing due
>> to Handler error.
>>
>> it's failing to parse the bucket policy document, but the error
>> message doesn't say what's wrong with it
>>
>> disabling rgw_policy_reject_invalid_principals might help if it's
>> failing on the Principal
>>
>> > Nov  7 22:51:40 ceph-05 radosgw[4054570]: req 13293029267332025583
>> 0.0s s3:list_bucket init_permissions on
>> :window-dev[1d0fa0b4-04eb-48f9-889b-a60de865ccd8.24143.10]) failed, ret=-13
>> > Nov  7 22:51:40 ceph-feed-05 radosgw[4054570]: req 13293029267332025583
>> 0.0s op->ERRORHANDLER: err_no=-13 new_err_no=-13
>> >
>> > ```
>> >
>> > Please help what's wrong here. We're in Ceph v17.2.7.
>> >
>> > Regards,
>> > Jayanth
>> >
>> > On Thu, Oct 26, 2023 at 7:14 PM Wesley Dillingham <
>> w...@wesdillingham.com> wrote:
>> >>
>> >> Thank you, this has worked to remove the policy.
>> >>
>> >> Respectfully,
>> >>
>> >> *Wes Dillingham*
>> >> w...@wesdillingham.com
>> >> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>> >>
>> >>
>> >> On Wed, Oct 25, 2023 at 5:10 PM Casey Bodley 
>> wrote:
>> >>
>> >> > On Wed, Oct 25, 2023 at 4:59 PM Wesley Dillingham <
>> w...@wesdillingham.com>
>> >> > wrote:
>> >> > >
>> >> > > Thank you, I am not sure (inherited cluster). I presume such an
>> admin
>> >> > user created after-the-fact would work?
>> >> >
>> >> > yes
>> >> >
>> >> > > Is there a good way to discover an admin user other than iterate
>> over
>> >> >

[kwin] [Bug 475062] Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

Wesley M  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #7 from Wesley M  ---
Sorry for the delay.

I can confirm that removing "ElectricBorderMaximise=false" from my kwinrc,
logging out, then logging back in resolved the issue. I'd never have caught
that. Thank you kindly.

Life demands my attention, but when I get time, I'll try to see if perhaps a
desktop effect or Kwin script added that line, and alert the appropriate
developer. Hoping I'm doing this correctly here, but marking as resolved. I
appreciate the help everyone.

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: [RBW] Re: Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

Hi Patrick!
I don't remember the hub, and I searched my email for hubs I bought in 2009 
– I was only able to find the one I built into the front wheel. However! 
This exercise show something loose in my head and I now recall how I made 
the monocog into a two-speed (before whatever I did to add a third cog). I 
replaced the locking by a fixed-gear cog. Here's a text diagram:

Your current setup has: spokes - spacer - splined cog - lockring

Change it to: spokes - splined cog - spacer - threaded cog

I hope this helps!
-Wes

On Saturday, October 28, 2023 at 9:51:46 PM UTC-7 Patrick Moore wrote:

> Do you recall the hub you used with the unicycle rim? I seem to recall BMX 
> freehubs that had room for 2 cogs.
>
> On Sat, Oct 28, 2023 at 9:16 PM Wesley  wrote:
>
>> Yeah, it looks marginal to get a second cog in there with a narrower 
>> spacer. According to Sheldon Brown, 9-speed cogs want a 2.54 mm spacer 
>> between the cogs: https://sheldonbrown.com/cribsheet-spacing.html
>>
>> I now remember that my monocog became a three speed after I built it a 
>> pair of winter wheels (I used a pair of very wide unicycle rims for maximum 
>> float). So I probably kept the original when intact and built a new hub 
>> into the new wheel. Sorry for not remembering, the bike has been out of my 
>> life for about eight years.
>>
>> -W
>> On Saturday, October 28, 2023 at 1:17:17 PM UTC-7 Patrick Moore wrote:
>>
>>> Wesley: Sorry, I missed this post in the thread volume.
>>>
>>> I'm pretty sure that my Monocog's freehub body takes only 1 cog; see 
>>> photo with single 3/32" cog and 2.5mm spacer: the splines end right after 
>>> the spacer.
>>>
>>> Am I looking at things right? I hesitate to remove the wheel because 
>>> getting the tire exactly centered in the chainstays, with 2-3 mm clearance 
>>> a side and the inevitable tire runout, while also adjusting chain tension 
>>> is a pain.
>>>
>>> [image: image.png]
>>>
>>> On Tue, Oct 17, 2023 at 3:56 PM Wesley  wrote:
>>>
>>>> Hey Patrick,
>>>> My recollection of my monocog was that the freehub had room for three 
>>>> cogs. I think there were spacers on the hub that covered up most of the 
>>>> free hub - remove the locking and you can do adjust the spacers as 
>>>> necessary. If yours is the same, then you could just keep that wheel and 
>>>> put the additional cogs onto it.
>>>>
>>>> And, in case I wasn't clear in my earlier response, I think there is 
>>>> plenty of adjustment room in the disc brakes to accommodate the rear axle 
>>>> being adjusted in the dropout.
>>>> -Wes
>>>>
>>>> On Tuesday, October 17, 2023 at 10:44:19 AM UTC-7 Patrick Moore wrote:
>>>>
>>>>> That's interesting, and after blundering into a few search result 
>>>>> pages about money markets and currency conversion I got:
>>>>>
>>>>> http://www.monebikes.com/read-me/
>>>>>
>>>>> But he says nothing about adjustable chainstays,
>>>>>
>>>>> Still, he does talk about weird possibilities like 3" tires and drop 
>>>>> bars, so I must investigate.
>>>>>
>>>>> Really, though, to conclude this question, it seems that I can either 
>>>>> have a very simple bike with disc brakes as long as it's a single speed, 
>>>>> or 
>>>>> I can accommodate 2 cogs using some niche, complex technology. I think 
>>>>> I'll 
>>>>> either settle for a fixed drivetrain (no rear brake, no problem) or get 
>>>>> off 
>>>>> and walk. Rear rim brake not option since I want to use disc rims.
>>>>>
>>>>> On Tue, Oct 17, 2023 at 8:44 AM Coal Bee Rye Anne <
>>>>> lionsrug...@gmail.com> wrote:
>>>>>
>>>>>> I have no personal experience with single speed disc nor 
>>>>>> Rocker/Slider or any of the existing dropout configurations being 
>>>>>> discussed 
>>>>>> other than keeping a mental catalogue and casual interest of such things 
>>>>>> as 
>>>>>> I discover them... but what about telescoping chainstays?   
>>>>>>
>>>>>> I recall seeing a few interesting options including a build that Rick 
>>>>>> Hunter did with a bottom bracket positioned wingnut to adjust chain 
>>>>>> tension 
>>>>>> with a form of te

Re: [RBW] Re: Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

Yeah, it looks marginal to get a second cog in there with a narrower 
spacer. According to Sheldon Brown, 9-speed cogs want a 2.54 mm spacer 
between the cogs: https://sheldonbrown.com/cribsheet-spacing.html

I now remember that my monocog became a three speed after I built it a pair 
of winter wheels (I used a pair of very wide unicycle rims for maximum 
float). So I probably kept the original when intact and built a new hub 
into the new wheel. Sorry for not remembering, the bike has been out of my 
life for about eight years.

-W
On Saturday, October 28, 2023 at 1:17:17 PM UTC-7 Patrick Moore wrote:

> Wesley: Sorry, I missed this post in the thread volume.
>
> I'm pretty sure that my Monocog's freehub body takes only 1 cog; see photo 
> with single 3/32" cog and 2.5mm spacer: the splines end right after the 
> spacer.
>
> Am I looking at things right? I hesitate to remove the wheel because 
> getting the tire exactly centered in the chainstays, with 2-3 mm clearance 
> a side and the inevitable tire runout, while also adjusting chain tension 
> is a pain.
>
> [image: image.png]
>
> On Tue, Oct 17, 2023 at 3:56 PM Wesley  wrote:
>
>> Hey Patrick,
>> My recollection of my monocog was that the freehub had room for three 
>> cogs. I think there were spacers on the hub that covered up most of the 
>> free hub - remove the locking and you can do adjust the spacers as 
>> necessary. If yours is the same, then you could just keep that wheel and 
>> put the additional cogs onto it.
>>
>> And, in case I wasn't clear in my earlier response, I think there is 
>> plenty of adjustment room in the disc brakes to accommodate the rear axle 
>> being adjusted in the dropout.
>> -Wes
>>
>> On Tuesday, October 17, 2023 at 10:44:19 AM UTC-7 Patrick Moore wrote:
>>
>>> That's interesting, and after blundering into a few search result pages 
>>> about money markets and currency conversion I got:
>>>
>>> http://www.monebikes.com/read-me/
>>>
>>> But he says nothing about adjustable chainstays,
>>>
>>> Still, he does talk about weird possibilities like 3" tires and drop 
>>> bars, so I must investigate.
>>>
>>> Really, though, to conclude this question, it seems that I can either 
>>> have a very simple bike with disc brakes as long as it's a single speed, or 
>>> I can accommodate 2 cogs using some niche, complex technology. I think I'll 
>>> either settle for a fixed drivetrain (no rear brake, no problem) or get off 
>>> and walk. Rear rim brake not option since I want to use disc rims.
>>>
>>> On Tue, Oct 17, 2023 at 8:44 AM Coal Bee Rye Anne  
>>> wrote:
>>>
>>>> I have no personal experience with single speed disc nor Rocker/Slider 
>>>> or any of the existing dropout configurations being discussed other than 
>>>> keeping a mental catalogue and casual interest of such things as I 
>>>> discover 
>>>> them... but what about telescoping chainstays?   
>>>>
>>>> I recall seeing a few interesting options including a build that Rick 
>>>> Hunter did with a bottom bracket positioned wingnut to adjust chain 
>>>> tension 
>>>> with a form of telescoping chainstay (I forget what that particular bike 
>>>> or 
>>>> design was referred to but I think it had a rigid fork, 26+ tires, disc 
>>>> brakes, upright riser Hunter bars, and a cow pattern custom frame bag... 
>>>> in 
>>>> case that helps ID it or dig something up for further review from the 
>>>> interwebs!)  
>>>>
>>>> Another is the design currently used by Cjell Mone of Mone Bikes 
>>>> referred to as the Mone Changer.  I couldn't find an actual page 
>>>> discussing 
>>>> or highlighting the chainstay design itself but believe he builds them 
>>>> into 
>>>> various frames as requested.  Here's a snippet from the FAQ page on his 
>>>> site.
>>>>
>>>> How do I work them Monē Changer dropouts?
>>>>
>>>>  - Remember, there are 5 (not 4, don't forget the caliper adaptor ones) 
>>>> bolts to loosen. To lengthen, sit on the saddle and hold the rear brake, 
>>>> give a couple gentle bounces...that should do it. To shorten, get your 
>>>> chain started on your single speed cog and chainring and pedal it around. 
>>>> straighten the tire in the chainstays and tighten 6 bolts. If you're 
>>>> running gears your penance is putting the bike in the stand, throwing a 
>>

[dspace-tech] I am trying to edit the frontend of dspace getting an error when I try to compile the files required for frontend by the command yarn build:prod

[Jefferson Wesley]

$ yarn run bulld:ssr $ ng build--configuration production &8 ng run dspace-
angular:s node: Internal/modules/cjs/loader: 1878 throw err; er:production 
A 

Error: Cannot find module './bootstrap'
Require stack: at Module._resolveFilename (node: Internal/modules/cjs/loader: 
1875:15)   
at Module._load (node: internal/modules/cjs/loader-928:27) 
 at Module.require (node: internal/modules/cjs/loader: 1141:19)
 at require (node: internal/modules/cjs/helpers:110:18)
 at Object. (/home/library/dspace-7.6-Frontend/node_modules/.bin/
ng:65:3) at Module._compile (node:internal/modules/cjs/loader: 1254:14)
 at Module._extensions..js (node: internal/modules/cjs/loader:1388:10)
 at Module load (node: internal/modules/cjs/loader:1117:32) 
at Module load (node:internal/modules/cjs/loader:958:12)
 at Function.executeUser EntryPoint [as runMain] (node: Internal/modules/
run_nain:81-12) { code: 'MODULE_NOT_FOUND",

requireStack: ['/home/library/dspace-7.6-frontend/node_modules/.bin/ng"]
Node.js v18.15.0 

error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this 
command.
error Command failed with exit code 1. I am getting this error 

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this 
command.

I tried online solutions but it didnt work. We are creating an institioanal 
repository for our college We are getting error when we try to compile 
frontend

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/905f3e87-b7ca-4bcf-b2d5-2c4eefcecd66n%40googlegroups.com.

[RBW] Re: New Member New Riv

[Wesley]

I've used the retainer nuts I save from old Presta inner tubes as the 
spacers for getting a clean, consistent gap when mounting a rear fender. 
Works great.
-Wes

On Thursday, October 26, 2023 at 6:18:46 AM UTC-7 greenteadrinkers wrote:

> Looks great! If you find yourself wanting to snug up the rear fender line, 
> V/O has a simple kit to do that (you could also get the parts from a 
> hardware store).
>
> https://velo-orange.com/collections/fender-parts/products/spring-thing
>
> Best,
> Scott
>
> On Wednesday, October 25, 2023 at 11:19:47 AM UTC-4 jim.me...@gmail.com 
> wrote:
>
>> [image: WIN_20231025_10_45_26_Pro.jpg][image: 
>> WIN_20231025_10_41_35_Pro.jpg]
>> My Joe is finally finished. I plan to tape the bar after the cockpit is 
>> dialed in. I did have a vintage XTR front mech, but it was a top pull and 
>> did not work. Other than that the bike is fantastic. Well - the vintage 
>> Wright saddle, given to me by a neighbor cleaning out his garage, is not 
>> great, but I will give it some time to break in.  This is the first bike I 
>> have ridden in years that is not clip in, and I am impressed with the grip 
>> of the MKS pedals. The IRD brake levers are a joy to operate. Also loving 
>> the dynamo and not having to worry about charging. This bike is my around 
>> town ride. 
>> On Friday, July 21, 2023 at 11:11:46 AM UTC-4 RBW Owners Bunch wrote:
>>
>>> Welcome Jim! I also bought one of the recent Appaloosas. I went with 
>>> Purple and Marks build option. Im glad to hear you’ve received yours as I’m 
>>> eagerly awaiting mine. Make sure to share a pic once it’s built up.
>>>
>>> On Friday, July 21, 2023 at 1:53:32 AM UTC-4 jim.me...@gmail.com wrote:
>>>
 Hi this is my first post. My lime green Appaloosa arrived last week and 
 I am looking forward to getting it built and ridden. I plan to use is as 
 my 
 commuter rig. 
 Jim

>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/fe01567c-e595-47d8-b66b-d150227e3a54n%40googlegroups.com.

[ceph-users] Re: owner locked out of bucket via bucket policy

[Wesley Dillingham]

Thank you, this has worked to remove the policy.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Oct 25, 2023 at 5:10 PM Casey Bodley  wrote:

> On Wed, Oct 25, 2023 at 4:59 PM Wesley Dillingham 
> wrote:
> >
> > Thank you, I am not sure (inherited cluster). I presume such an admin
> user created after-the-fact would work?
>
> yes
>
> > Is there a good way to discover an admin user other than iterate over
> all users and retrieve user information? (I presume radosgw-admin user info
> --uid=" would illustrate such administrative access?
>
> not sure there's an easy way to search existing users, but you could
> create a temporary admin user for this repair
>
> >
> > Respectfully,
> >
> > Wes Dillingham
> > w...@wesdillingham.com
> > LinkedIn
> >
> >
> > On Wed, Oct 25, 2023 at 4:41 PM Casey Bodley  wrote:
> >>
> >> if you have an administrative user (created with --admin), you should
> >> be able to use its credentials with awscli to delete or overwrite this
> >> bucket policy
> >>
> >> On Wed, Oct 25, 2023 at 4:11 PM Wesley Dillingham <
> w...@wesdillingham.com> wrote:
> >> >
> >> > I have a bucket which got injected with bucket policy which locks the
> >> > bucket even to the bucket owner. The bucket now cannot be accessed
> (even
> >> > get its info or delete bucket policy does not work) I have looked in
> the
> >> > radosgw-admin command for a way to delete a bucket policy but do not
> see
> >> > anything. I presume I will need to somehow remove the bucket policy
> from
> >> > however it is stored in the bucket metadata / omap etc. If anyone can
> point
> >> > me in the right direction on that I would appreciate it. Thanks
> >> >
> >> > Respectfully,
> >> >
> >> > *Wes Dillingham*
> >> > w...@wesdillingham.com
> >> > LinkedIn <http://www.linkedin.com/in/wesleydillingham>
> >> > ___
> >> > ceph-users mailing list -- ceph-users@ceph.io
> >> > To unsubscribe send an email to ceph-users-le...@ceph.io
> >> >
> >>
>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: owner locked out of bucket via bucket policy

[Wesley Dillingham]

Thank you, I am not sure (inherited cluster). I presume such an admin user
created after-the-fact would work? Is there a good way to discover an admin
user other than iterate over all users and retrieve user information? (I
presume radosgw-admin user info --uid=" would illustrate such
administrative access?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Oct 25, 2023 at 4:41 PM Casey Bodley  wrote:

> if you have an administrative user (created with --admin), you should
> be able to use its credentials with awscli to delete or overwrite this
> bucket policy
>
> On Wed, Oct 25, 2023 at 4:11 PM Wesley Dillingham 
> wrote:
> >
> > I have a bucket which got injected with bucket policy which locks the
> > bucket even to the bucket owner. The bucket now cannot be accessed (even
> > get its info or delete bucket policy does not work) I have looked in the
> > radosgw-admin command for a way to delete a bucket policy but do not see
> > anything. I presume I will need to somehow remove the bucket policy from
> > however it is stored in the bucket metadata / omap etc. If anyone can
> point
> > me in the right direction on that I would appreciate it. Thanks
> >
> > Respectfully,
> >
> > *Wes Dillingham*
> > w...@wesdillingham.com
> > LinkedIn <http://www.linkedin.com/in/wesleydillingham>
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
> >
>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] owner locked out of bucket via bucket policy

[Wesley Dillingham]

I have a bucket which got injected with bucket policy which locks the
bucket even to the bucket owner. The bucket now cannot be accessed (even
get its info or delete bucket policy does not work) I have looked in the
radosgw-admin command for a way to delete a bucket policy but do not see
anything. I presume I will need to somehow remove the bucket policy from
however it is stored in the bucket metadata / omap etc. If anyone can point
me in the right direction on that I would appreciate it. Thanks

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: support new

[Wesley MOUEDINE ASSABY]

Hello Ingo,

Parfait, merci beaucoup.

Regards,

Wesley

-Message d'origine-
De : Ingo Schwarze  
Envoyé : mardi 24 octobre 2023 15:35
À : Wesley MOUEDINE ASSABY 
Cc : misc@openbsd.org
Objet : Re: support new

Hi Wesley,

Wesley MOUEDINE ASSABY wrote on Tue, Oct 24, 2023 at 02:06:47PM +0400:

> 0
> C France
> P REUNION
> T Sainte Clotilde
> Z 97490
> O Consultant
> I Wesley Mouedine Assaby
> M wes...@mouedine.net <mailto:wes...@mouedine.net> U 
> https://www.mouedine.net N OpenBSD consulting, services like 
> mailserver, web hosting, firewall and vpn.

Committed with s/vpn/VPN/, the spelling familiar from OpenBSD manual pages.
I removed all information from your old entry that you no longer included in
your new entry.

The new entry is now online here, please check:

  https://www.openbsd.org/support.html#France

Yours,
  Ingo

support update

[Wesley MOUEDINE ASSABY]

Please, can you remove my old entry < AISE-INFORMATIQUE > in < France >
area.

Thank's !

 

support new

[Wesley MOUEDINE ASSABY]

0

C France

P REUNION

T Sainte Clotilde

Z 97490

O Consultant

I Wesley Mouedine Assaby

M wes...@mouedine.net <mailto:wes...@mouedine.net> 

U https://www.mouedine.net

N OpenBSD consulting, services like mailserver, web hosting, firewall and
vpn.

 

 

 

[RBW] Re: Boise to San Francisco bicycle route

[Wesley]

I rode down the Pacific coast about a decade ago, and now live in 
Sacramento. I'd definitely prefer to hit the coast in the north (even 
follow the Columbia to the coast?) or cross the Sierra near Tahoe, rather 
than coming down the Central Valley. Other than that, not a lot to add. Are 
you looking to ride roads the whole way, or use trails/gravel roads?
-Wes

On Monday, October 23, 2023 at 3:07:37 PM UTC-7 Jim S. wrote:

> Hi, I understand that I can use Google or other sources to research a 
> preferable route. But I was wondering if anyone in the group has done all 
> or part of this ride? I"d be curious about routes you chose, etc. 
>
> Thank you for any ideas.
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/17c17436-36e3-453a-ac49-6ce4cceb0115n%40googlegroups.com.

[alto] Iotdir telechat review of draft-ietf-alto-new-transport-17

[Wesley Eddy via Datatracker]

Reviewer: Wesley Eddy
Review result: Ready with Issues

I only found 1 real "issue" in reading this document, and a few smaller nits,
described below.  None of these comments are specifically related to IoTDIR
type of concerns, and it doesn't seem like the protocol would be intended for
use in IoT.

Issues:

1) The placement of TIPS relative to other ALTO standards is unclear.  This
became evident to me on page 4, reading the bottom paragraph with "Despite the
benefits, however, ...".  Is the gist of this paragraph supposed to be that the
WG does not think that TIPS should totally replace ALTO/SSE?  It's not clear to
me what the recommendation or applicability statement for these is in practical
terms.  The WG should convey more clearly what it believes implemenentations
and deployments should be using, under what circumstances.  If both protocols
are maintained as standards track, then it should be clearly stated why that
needs to be the case and that this does not obsolete ALTO/SSE.  It seems to be
created as another option, with unclear guidance provided to implementers about
what to do.

Nits:

1) page 4
from
"no capability it transmits incremental"
to
"no capability to transmit incremental"

2) I don't know if this is typical for other ALTO documents, but the usage of
the term "transport protocol" in the first paragraph of section 1 is not
consistent with the Internet architecture where "transport protocols" are TCP,
UDP, SCTP, etc., nor is it "transport" in the sense of MPLS, etc.   I would
suggest using the alternative term "transfer" to be less jarring.  Of course,
if this is already the standard terminology for ALTO that the IETF has
accepted, then this comment can be ignored.

3) In the section 5.4 example, should "my-networkmap" in some of the "uses"
values by "my-network-map" that was defined at the top?



___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: Crash on TOSHIBA PORTEGE Z30-A laptop

[wesley]

> If there isn't a newer BIOS that resolves this, I would tend to return the 
> box as not suitable.



This is the case, there’s no BIOS update.

Thank you very much, anyway.

Cheers,


/Wesley

 

De : Philip Guenther  
Envoyé : lundi 23 octobre 2023 00:39
À : wes...@technicien.io
Cc : bugs@openbsd.org; m...@openbsd.org
Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop

 

On Sat, Oct 21, 2023 at 2:27 AM mailto:wes...@technicien.io> > wrote:

Hi Philip,

Thank you very much for your answer.

I tried to disable all options (+devices) possible. Same issue.
And what's about disable acpi in the kernel using the bsd.re-config?

 

As Mike and Theo noted, this will certainly cause problems.

 

 

Do you think If I replace the wireless card by somthing else, It could resolve 
this issue?

 

Very unlikely.  The problem is the stack depth of the ACPI processing.  The 
crash you saw had the wifi interrupt occur during the ACPI processing but it 
could just as well happen with some other device interrupting the ACPI 
processing.

 

If there isn't a newer BIOS that resolves this, I would tend to return the box 
as not suitable.

 

 

Phlip Guenther

Re: Crash on TOSHIBA PORTEGE Z30-A laptop

[wesley]

> If there isn't a newer BIOS that resolves this, I would tend to return the 
> box as not suitable.



This is the case, there’s no BIOS update.

Thank you very much, anyway.

Cheers,


/Wesley

 

De : Philip Guenther  
Envoyé : lundi 23 octobre 2023 00:39
À : wes...@technicien.io
Cc : b...@openbsd.org; misc@openbsd.org
Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop

 

On Sat, Oct 21, 2023 at 2:27 AM mailto:wes...@technicien.io> > wrote:

Hi Philip,

Thank you very much for your answer.

I tried to disable all options (+devices) possible. Same issue.
And what's about disable acpi in the kernel using the bsd.re-config?

 

As Mike and Theo noted, this will certainly cause problems.

 

 

Do you think If I replace the wireless card by somthing else, It could resolve 
this issue?

 

Very unlikely.  The problem is the stack depth of the ACPI processing.  The 
crash you saw had the wifi interrupt occur during the ACPI processing but it 
could just as well happen with some other device interrupting the ACPI 
processing.

 

If there isn't a newer BIOS that resolves this, I would tend to return the box 
as not suitable.

 

 

Phlip Guenther

[kwin] [Bug 475062] Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

--- Comment #5 from Wesley M  ---
Apologies. I didn't know I should manually update the bug status. It seems like
something that would interfere with the person helping work on the bug, so the
idea didn't even occur to me. It's updated now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475062] Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

Wesley M  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: Crash on TOSHIBA PORTEGE Z30-A laptop

[wesley]

Hi Philip,

Thank you very much for your answer.

I tried to disable all options (+devices) possible. Same issue.
And what's about disable acpi in the kernel using the bsd.re-config?

Do you think If I replace the wireless card by somthing else, It could resolve 
this issue?


/Wesley 



-Message d'origine-
De : owner-b...@openbsd.org  De la part de Philip 
Guenther
Envoyé : samedi 21 octobre 2023 03:23
À : wes...@technicien.io
Cc : bugs@openbsd.org; m...@openbsd.org
Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop

On Fri, Oct 20, 2023 at 1:23 PM  wrote:

> I've recently installed OpenBSD 7.4 on this laptop.
>
> However, I'm experiencing random crashes. These occur at various 
> times, including during kernel loading (before running /etc/rc),
>
> or later while I'm using the system.
>
>
> I've included the contents of /var/run/dmesg.boot below and attached 
> the screens with the ddb output command.
>
...

> bios0: vendor TOSHIBA version "Version 4.30" date 04/26/2018
>

The screenshots show that the fault happens during a wifi interrupt that 
catches the ACPI thread processing a very deeply nested AML code.  I suspect 
it's actually running out of kernel stack space as a result.
Everything below is based on that hypothesis.

So, the first thing to try is to see if there's a BIOS update newer than the 
2018 rev it currently has.  They may have optimized the AML code, or at least 
made it less deeply nested.

Another possibility is to see if there's a device you can disable that would 
result in that AML not being called.  If there's anything that you aren't using 
then disable it in the BIOS and hope.

The last possibility would be to build a kernel which allocates more pages per 
thread for its kernel stack by bumping the UPAGES #define in 
/usr/src/sys/arch/amd64/include/param.h and building a new kernel.  It's really 
only the ACPI thread that needs this, but we don't currently have code to 
control that on a per-thread basis.


Philip Guenther

Re: Crash on TOSHIBA PORTEGE Z30-A laptop

[wesley]

Hi Philip,

Thank you very much for your answer.

I tried to disable all options (+devices) possible. Same issue.
And what's about disable acpi in the kernel using the bsd.re-config?

Do you think If I replace the wireless card by somthing else, It could resolve 
this issue?


/Wesley 



-Message d'origine-
De : owner-b...@openbsd.org  De la part de Philip 
Guenther
Envoyé : samedi 21 octobre 2023 03:23
À : wes...@technicien.io
Cc : b...@openbsd.org; misc@openbsd.org
Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop

On Fri, Oct 20, 2023 at 1:23 PM  wrote:

> I've recently installed OpenBSD 7.4 on this laptop.
>
> However, I'm experiencing random crashes. These occur at various 
> times, including during kernel loading (before running /etc/rc),
>
> or later while I'm using the system.
>
>
> I've included the contents of /var/run/dmesg.boot below and attached 
> the screens with the ddb output command.
>
...

> bios0: vendor TOSHIBA version "Version 4.30" date 04/26/2018
>

The screenshots show that the fault happens during a wifi interrupt that 
catches the ACPI thread processing a very deeply nested AML code.  I suspect 
it's actually running out of kernel stack space as a result.
Everything below is based on that hypothesis.

So, the first thing to try is to see if there's a BIOS update newer than the 
2018 rev it currently has.  They may have optimized the AML code, or at least 
made it less deeply nested.

Another possibility is to see if there's a device you can disable that would 
result in that AML not being called.  If there's anything that you aren't using 
then disable it in the BIOS and hope.

The last possibility would be to build a kernel which allocates more pages per 
thread for its kernel stack by bumping the UPAGES #define in 
/usr/src/sys/arch/amd64/include/param.h and building a new kernel.  It's really 
only the ACPI thread that needs this, but we don't currently have code to 
control that on a per-thread basis.


Philip Guenther

Re: [RBW] Re: Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

Ah. Can you not remove the 5mm spacer? That should be enough room for a 
second cog, IMO.
-W

On Tuesday, October 17, 2023 at 3:02:19 PM UTC-7 Patrick Moore wrote:

> Not mine, said by seller to be a 2012 model. I have a 5 mm spacer, then 
> the 3/32" cog, and then the lockring threads.
>
> Good to know that the caliper (again, list, almost vertically atop the 
> rotor at top dead center, but actually offset a cm or two forward) can 
> accommodate a bit of fore/aft axle movement.
>
> On Tue, Oct 17, 2023 at 3:56 PM Wesley  wrote:
>
>> Hey Patrick,
>> My recollection of my monocog was that the freehub had room for three 
>> cogs. I think there were spacers on the hub that covered up most of the 
>> free hub - remove the locking and you can do adjust the spacers as 
>> necessary. If yours is the same, then you could just keep that wheel and 
>> put the additional cogs onto it.
>>
>> And, in case I wasn't clear in my earlier response, I think there is 
>> plenty of adjustment room in the disc brakes to accommodate the rear axle 
>> being adjusted in the dropout.
>> -Wes
>>
>> On Tuesday, October 17, 2023 at 10:44:19 AM UTC-7 Patrick Moore wrote:
>>
>>> That's interesting, and after blundering into a few search result pages 
>>> about money markets and currency conversion I got:
>>>
>>> http://www.monebikes.com/read-me/
>>>
>>> But he says nothing about adjustable chainstays,
>>>
>>> Still, he does talk about weird possibilities like 3" tires and drop 
>>> bars, so I must investigate.
>>>
>>> Really, though, to conclude this question, it seems that I can either 
>>> have a very simple bike with disc brakes as long as it's a single speed, or 
>>> I can accommodate 2 cogs using some niche, complex technology. I think I'll 
>>> either settle for a fixed drivetrain (no rear brake, no problem) or get off 
>>> and walk. Rear rim brake not option since I want to use disc rims.
>>>
>>> On Tue, Oct 17, 2023 at 8:44 AM Coal Bee Rye Anne  
>>> wrote:
>>>
>>>> I have no personal experience with single speed disc nor Rocker/Slider 
>>>> or any of the existing dropout configurations being discussed other than 
>>>> keeping a mental catalogue and casual interest of such things as I 
>>>> discover 
>>>> them... but what about telescoping chainstays?   
>>>>
>>>> I recall seeing a few interesting options including a build that Rick 
>>>> Hunter did with a bottom bracket positioned wingnut to adjust chain 
>>>> tension 
>>>> with a form of telescoping chainstay (I forget what that particular bike 
>>>> or 
>>>> design was referred to but I think it had a rigid fork, 26+ tires, disc 
>>>> brakes, upright riser Hunter bars, and a cow pattern custom frame bag... 
>>>> in 
>>>> case that helps ID it or dig something up for further review from the 
>>>> interwebs!)  
>>>>
>>>> Another is the design currently used by Cjell Mone of Mone Bikes 
>>>> referred to as the Mone Changer.  I couldn't find an actual page 
>>>> discussing 
>>>> or highlighting the chainstay design itself but believe he builds them 
>>>> into 
>>>> various frames as requested.  Here's a snippet from the FAQ page on his 
>>>> site.
>>>>
>>>> How do I work them Monē Changer dropouts?
>>>>
>>>>  - Remember, there are 5 (not 4, don't forget the caliper adaptor ones) 
>>>> bolts to loosen. To lengthen, sit on the saddle and hold the rear brake, 
>>>> give a couple gentle bounces...that should do it. To shorten, get your 
>>>> chain started on your single speed cog and chainring and pedal it around. 
>>>> straighten the tire in the chainstays and tighten 6 bolts. If you're 
>>>> running gears your penance is putting the bike in the stand, throwing a 
>>>> foot on the BB and pulling the rim to the front.
>>>>
>>>>
>>>> Since you are going the custom route for this hypothetical bike I 
>>>> figured I'd add these possibilities to the mix : )
>>>> On Sunday, October 15, 2023 at 6:12:06 PM UTC-4 Patrick Moore wrote:
>>>>
>>>>> Thinking out loud; help me clarify my thoughts.
>>>>>
>>>>> I think of devising a Monocog replacement, with 622X76/29X3" wheels, 
>>>>> but instead of a mono cog, with a duo cog. This hypothetical bike would 
>>>>

Re: [RBW] Re: Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

Hey Patrick,
My recollection of my monocog was that the freehub had room for three cogs. 
I think there were spacers on the hub that covered up most of the free hub 
- remove the locking and you can do adjust the spacers as necessary. If 
yours is the same, then you could just keep that wheel and put the 
additional cogs onto it.

And, in case I wasn't clear in my earlier response, I think there is plenty 
of adjustment room in the disc brakes to accommodate the rear axle being 
adjusted in the dropout.
-Wes

On Tuesday, October 17, 2023 at 10:44:19 AM UTC-7 Patrick Moore wrote:

> That's interesting, and after blundering into a few search result pages 
> about money markets and currency conversion I got:
>
> http://www.monebikes.com/read-me/
>
> But he says nothing about adjustable chainstays,
>
> Still, he does talk about weird possibilities like 3" tires and drop bars, 
> so I must investigate.
>
> Really, though, to conclude this question, it seems that I can either have 
> a very simple bike with disc brakes as long as it's a single speed, or I 
> can accommodate 2 cogs using some niche, complex technology. I think I'll 
> either settle for a fixed drivetrain (no rear brake, no problem) or get off 
> and walk. Rear rim brake not option since I want to use disc rims.
>
> On Tue, Oct 17, 2023 at 8:44 AM Coal Bee Rye Anne  
> wrote:
>
>> I have no personal experience with single speed disc nor Rocker/Slider or 
>> any of the existing dropout configurations being discussed other than 
>> keeping a mental catalogue and casual interest of such things as I discover 
>> them... but what about telescoping chainstays?   
>>
>> I recall seeing a few interesting options including a build that Rick 
>> Hunter did with a bottom bracket positioned wingnut to adjust chain tension 
>> with a form of telescoping chainstay (I forget what that particular bike or 
>> design was referred to but I think it had a rigid fork, 26+ tires, disc 
>> brakes, upright riser Hunter bars, and a cow pattern custom frame bag... in 
>> case that helps ID it or dig something up for further review from the 
>> interwebs!)  
>>
>> Another is the design currently used by Cjell Mone of Mone Bikes referred 
>> to as the Mone Changer.  I couldn't find an actual page discussing or 
>> highlighting the chainstay design itself but believe he builds them into 
>> various frames as requested.  Here's a snippet from the FAQ page on his 
>> site.
>>
>> How do I work them Monē Changer dropouts?
>>
>>  - Remember, there are 5 (not 4, don't forget the caliper adaptor ones) 
>> bolts to loosen. To lengthen, sit on the saddle and hold the rear brake, 
>> give a couple gentle bounces...that should do it. To shorten, get your 
>> chain started on your single speed cog and chainring and pedal it around. 
>> straighten the tire in the chainstays and tighten 6 bolts. If you're 
>> running gears your penance is putting the bike in the stand, throwing a 
>> foot on the BB and pulling the rim to the front.
>>
>>
>> Since you are going the custom route for this hypothetical bike I figured 
>> I'd add these possibilities to the mix : )
>> On Sunday, October 15, 2023 at 6:12:06 PM UTC-4 Patrick Moore wrote:
>>
>>> Thinking out loud; help me clarify my thoughts.
>>>
>>> I think of devising a Monocog replacement, with 622X76/29X3" wheels, but 
>>> instead of a mono cog, with a duo cog. This hypothetical bike would have 
>>> disc brakes. I don't want to use a chain tensioner, and I prefer to take 
>>> advantage of the greater gear ratio differences between cogs of different 
>>> sizes compared to rings with the same tooth differences, and of the 
>>> consequent smaller axle movement required to adjust chain slack, so the 
>>> multiple cogs would be in the back and not on the crank.
>>>
>>> On my beloved 1999 Joe Starck Riv Road Custom fixie I use a 17/19 Dingle 
>>> on a Phil hub with a QR axle; it's very easy to stop, flip the QR lever, 
>>> move the chain, align the wheel, and tighten the QR.
>>>
>>> That's what I imagine for the Monocog replacement.
>>>
>>> 1. Disc brakes. But this bike would have disc brakes. I'd probably not 
>>> need more than a 2-t cog difference, but will your typical caliper/rotor 
>>> setup accept the 1/4" axle movement? (1/8" of axle movement is required -- 
>>> so they say; I've never measured it and take it on faith -- to accomodate a 
>>> 1 tooth sprocket difference.)
>>>
>>> 2. Two cogs. How to get 2 cogs onto a suitable "ss" hub with a 
>>> freewheel. The DIngle isn't made anymore and in any event wasn't made -- am 
>>> I right? -- with 2-teeth gaps. The Monocog has a freehub designed to take 1 
>>> single Shimano-spline-type cog; there's no room for a second cog. >>>What 
>>> options does one have to get 2 cogs with a 2-tooth difference onto a hub 
>>> suitable for a QR axle?
>>>
>>> I realize that I could just use an old 7 speed Shimano freehub, and I 
>>> might end up doing that, but I'd prefer to have a hub that does not require 

[ceph-users] Re: How do you handle large Ceph object storage cluster?

[Wesley Dillingham]

Well you are probably in the top 1% of cluster size. I would guess that
trying to cut your existing cluster in half while not encountering any
downtime as you shuffle existing buckets between old cluster and new
cluster would be harder than redirecting all new buckets (or users) to a
second cluster. Obviously you will need to account for each cluster having
a single bucket namespace when attempting to redirect requests to a cluster
of clusters. Lots of ways to skin this cat and it would be a large and
complicated architectural undertaking.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Oct 16, 2023 at 10:53 AM  wrote:

> Hi Everyone,
>
> My company is dealing with quite large Ceph cluster (>10k OSDs, >60 PB of
> data). It is entirely dedicated to object storage with S3 interface.
> Maintenance and its extension are getting more and more problematic and
> time consuming. We consider to split it to two or more completely separate
> clusters (without replication of data among them) and create S3 layer of
> abstraction with some additional metadata that will allow us to use these
> 2+ physically independent instances as a one logical cluster. Additionally,
> newest data is the most demanded data, so we have to spread it equally
> among clusters to avoid skews in cluster load.
>
> Do you have any similar experience? How did you handle it? Maybe you have
> some advice? I'm not a Ceph expert. I'm just a Ceph's user and software
> developer who does not like to duplicate someone's job.
>
> Best,
> Paweł
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: aluminum V steel rear rack

[Wesley]

I'm pretty sure I've only ever had aluminum racks. They take serious abuse 
without complaint.
-Wes

On Monday, October 16, 2023 at 6:47:13 AM UTC-7 ber...@bernardduhon.com 
wrote:

>  
>
>  
>
> Folks,
>
> I outfitted my Waterford Tourer with aluminum rear rack .
>
>  
>
> Load was like 20 pd rear 12 pd front.  Mostly good roads w/ a little 
> gravel for a week
>
>  
>
> I found it handled well. 
>
>  
>
> I have an Indy Fab sport tourer converted to 650b.  I am thinking that 
> aluminum   might work.
>
> Anticipate 1 week of same touring. 
>
>  
>
> What say ye?  
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/89d2669c-b339-414d-be7e-7944832b84ccn%40googlegroups.com.

Re: [RBW] Best way to arrange 2-cog manual shifting for "single speed" disc braked bicycle

[Wesley]

When I was using a monocog 29er as my winter bike, I had a triple speed: 
three cogs, three chainrings (the third, lowest gear was used for maximum 
torque to drive through deep snow without bogging down) . All three combos 
added up to the same total teeth but the change in angles was enough that I 
usually had to adjust the wheel in the dropout when changing gears. It 
worked fine with the disc brakes.
-W

On Monday, October 16, 2023 at 11:31:14 AM UTC-7 Patrick Moore wrote:

> Thanks, Dave, good to know about the DOX 2-tooth gap fws.
>
> Back to the question of disc brake and axle movement: the *chain length* will 
> remain the same; the axle will have to move to accommodate different size 
> cogs since I don't want a tensioner.* This of course assumes that one is 
> using horizontal dropouts or track ends; I'd like to stay with that 
> assumption until it is entirely and definitely ruled out.
>
> When moving the chain from a 17 to to a 19 t cog and v/v the axle should 
> have to move only 1/4" or ~6 mm. This movement would be back to front and 
> v/v. 
>
> The rear caliper on the Monocog is  mounted *above* the rotor (actually, 
> it seems to be a wee bit forward of the rotor centerline). Couldn't you 
> mount the caliper at top dead center of the rotor? And if so mounted, the 
> rotor would move only ~3 mm forward or back for a 2-tooth axle shift.
>
> Could the caliper not accommodate a 1/8" or 3 mm movement fore and aft? If 
> I have to specify a particular disc brake, let's just say a cable operated 
> BB7.
>
> I'll think more about the 2 rings/2 cogs arrangement. I could use, say, a 
> 36X17 and 34 X 19 for 65" and 55". And certainly, a vertical dropout would 
> be much easier to use for manual chain shifting than track ends.
>
> Or one could use a kickback hub: 32 X 21 for a 46" gear in direct, 64" in 
> 138% overdrive. 
>
> All in all, I think I prefer the QR and horizontal dropout system, and if 
> disc brakes can't accomodate this then I'll stick to a single speed. [Or, I 
> could go back to a fixed off road bike where I wouldn't need a rear brake; 
> but I rather think I want a freewheel.
>
> *The reason might sound silly but it's a valid one: One reason I took the 
> Monocog in trade was to have a snow bike. We very rarely get enough snow to 
> ride in but we do get a few days per year and I like riding in it. A few 
> years ago I found that wet gummy snow clogged the cassette and rear 
> derailleur of my Matthews and made the chain skip. Thus the thought of 
> getting a snow/sand single speed with 3" tires.
>
>
>
> On Sun, Oct 15, 2023 at 8:51 PM DavidP  wrote:
>
>> Patrick, I hope I am understanding what you are looking for, but the DOS 
>> freewheels are still made in the two tooth differential versions; it's only 
>> the three tooth differential version (16/19) that was discontinued.
>>
>> I'm not sure if you are looking for DOS freewheels in this situation 
>> though as these are thread on and not splined
>> If you are looking at a different wheelset on this hypothetical bike and 
>> a standard single speed threaded hub then the DOS will work:
>> https://www.whiteind.com/product/double-freewheels
>>
>> Regarding disc brakes, to Eric's point I know of no way to have the quick 
>> change of gearing you are looking for with non constant chain length and a 
>> rear disc. Most single speed disc options that carry the disc with the 
>> wheel use sliding or swinging dropouts but these are not really something 
>> you want to be adjusting on the fly.
>>
>> A double chainring setup really is the simplest. It's a quick change and 
>> adds a few seconds to the process.
>>
>> If you adopt a constant chain length dual ring/cog setup, sliding 
>> dropouts (or an EBB) make the change even quicker as you just drop the 
>> wheel, swap the cog/ring and reinsert.
>>
>> -Dave
>>
>> On Sunday, October 15, 2023 at 10:19:14 PM UTC-4 Patrick Moore wrote:
>>
>>> Thanks, but I don't want that complication. I want (if I can get it) the 
>>> simplicity of my Riv customer gofast: QR rear hub, Dingle cog, long 
>>> horizontal dropouts. I don't necessarily need these means but I do want the 
>>> same end.
>>>
>>> On Sun, Oct 15, 2023 at 4:31 PM Eric Daume  wrote:
>>>
 The simplest solution is to also use two chainrings, matching the cog 
 difference (for instance, with a 16/18 Dos freewheel, use 42 and 44t 
 chainrings). Then the 44/16 and 42/18 have the same chain length, and the 
 rotor to pad relationship doesn't change.

 Or just use a disc front and a rim brake rear, and a forward facing 
 horizontal dropout (like typical UJBs have)

 Eric

 On Sun, Oct 15, 2023 at 6:12 PM Patrick Moore  
 wrote:

> Thinking out loud; help me clarify my thoughts.
>
> I think of devising a Monocog replacement, with 622X76/29X3" wheels, 
> but instead of a mono cog, with a duo cog. This hypothetical bike would 
> have disc brakes. I don't want to use a chain 

[kwin] [Bug 475064] Bizarre graphical glitches on half of one screen with complex triple-monitor arrangement

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475064

--- Comment #6 from Wesley M  ---
(In reply to Nate Graham from comment #4)
> What GPU hardware are you using on this system?

I see the bug has already been marked as duplicate, but to answer your
question, it's an AMD RX 580. The issue occurs even when there are no windows
open on the monitor, and even when the system is sitting idle. It's unclear
what the cause is.

-- 
You are receiving this mail because:
You are watching all bug changes.

[pfx] user based transport

[wesley--- via Postfix-users]

Hello,

How can I setup username based transport?
for incoming messages, such as use...@foo.com will be delivered to host a.
use...@foo.com will be delivered to host b.

Thanks.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

[ceph-users] Re: Unable to fix 1 Inconsistent PG

[Wesley Dillingham]

Just to be clear, you should remove the osd by stopping the daemon and
marking it out before you repair the PG. The pg may not be able to be
repaired until you remove the bad disk.

1 - identify the bad disk (via scrubs or SMART/dmesg inspection)
2 - stop daemon and mark it out
3 - wait for PG to finish backfill
4 - issue the pg repair

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Wed, Oct 11, 2023 at 4:38 PM Wesley Dillingham 
wrote:

> If I recall correctly When the acting or up_set of an PG changes the scrub
> information is lost. This was likely lost when you stopped osd.238 and
> changed the sets.
>
> I do not believe based on your initial post you need to be using the
> objectstore tool currently. Inconsistent PGs are a common occurrence and
> can be repaired.
>
> After your most recent post I would get osd.238 back in the cluster unless
> you have reason to believe it is the failing hardware. But it could be any
> of the osds in the following set (from your initial post)
> [238,106,402,266,374,498,590,627,684,73,66]
>
> You should inspect the SMART data and dmesg on the drives and servers
> supporting the above OSDs to determine which one is failing.
>
> After you get the PG back to active+clean+inconsistent (get osd.238 back
> in and it finishes its backfill) you can re-issue a manual deep-scrub of it
> and once that deep-scrub finishes the rados list-inconsistent-obj 15.f4f
> should return and implicate a single osd with errors.
>
> Finally you should issue the PG repair again.
>
> In order to get your manually issued scrubs and repairs to start sooner
> you may want to set the noscrub and nodeep-scrub flags until you can get
> your PG repaired.
>
> As an aside osd_max_scrubs of 9 is too aggressive IMO I would drop that
> back to 3, max
>
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Wed, Oct 11, 2023 at 10:51 AM Siddhit Renake 
> wrote:
>
>> Hello Wes,
>>
>> Thank you for your response.
>>
>> brc1admin:~ # rados list-inconsistent-obj 15.f4f
>> No scrub information available for pg 15.f4f
>>
>> brc1admin:~ # ceph osd ok-to-stop osd.238
>> OSD(s) 238 are ok to stop without reducing availability or risking data,
>> provided there are no other concurrent failures or interventions.
>> 341 PGs are likely to be degraded (but remain available) as a result.
>>
>> Before I proceed with your suggested action plan, needed clarification on
>> below.
>> In order to list all objects residing on the inconsistent PG, we had
>> stopped the primary osd (osd.238) and extracted the list of all objects
>> residing on this osd using ceph-objectstore tool. We notice that that when
>> we stop the osd (osd.238) using systemctl, RGW gateways continuously
>> restarts which is impacting our S3 service availability. This was observed
>> twice when we stopped osd.238 for general maintenance activity w.r.t
>> ceph-objectstore tool. How can we ensure that stopping and marking out
>> osd.238 ( primary osd of inconsistent pg) does not impact RGW service
>> availability ?
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Unable to fix 1 Inconsistent PG

[Wesley Dillingham]

If I recall correctly When the acting or up_set of an PG changes the scrub
information is lost. This was likely lost when you stopped osd.238 and
changed the sets.

I do not believe based on your initial post you need to be using the
objectstore tool currently. Inconsistent PGs are a common occurrence and
can be repaired.

After your most recent post I would get osd.238 back in the cluster unless
you have reason to believe it is the failing hardware. But it could be any
of the osds in the following set (from your initial post)
[238,106,402,266,374,498,590,627,684,73,66]

You should inspect the SMART data and dmesg on the drives and servers
supporting the above OSDs to determine which one is failing.

After you get the PG back to active+clean+inconsistent (get osd.238 back in
and it finishes its backfill) you can re-issue a manual deep-scrub of it
and once that deep-scrub finishes the rados list-inconsistent-obj 15.f4f
should return and implicate a single osd with errors.

Finally you should issue the PG repair again.

In order to get your manually issued scrubs and repairs to start sooner you
may want to set the noscrub and nodeep-scrub flags until you can get your
PG repaired.

As an aside osd_max_scrubs of 9 is too aggressive IMO I would drop that
back to 3, max


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Wed, Oct 11, 2023 at 10:51 AM Siddhit Renake 
wrote:

> Hello Wes,
>
> Thank you for your response.
>
> brc1admin:~ # rados list-inconsistent-obj 15.f4f
> No scrub information available for pg 15.f4f
>
> brc1admin:~ # ceph osd ok-to-stop osd.238
> OSD(s) 238 are ok to stop without reducing availability or risking data,
> provided there are no other concurrent failures or interventions.
> 341 PGs are likely to be degraded (but remain available) as a result.
>
> Before I proceed with your suggested action plan, needed clarification on
> below.
> In order to list all objects residing on the inconsistent PG, we had
> stopped the primary osd (osd.238) and extracted the list of all objects
> residing on this osd using ceph-objectstore tool. We notice that that when
> we stop the osd (osd.238) using systemctl, RGW gateways continuously
> restarts which is impacting our S3 service availability. This was observed
> twice when we stopped osd.238 for general maintenance activity w.r.t
> ceph-objectstore tool. How can we ensure that stopping and marking out
> osd.238 ( primary osd of inconsistent pg) does not impact RGW service
> availability ?
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Unable to fix 1 Inconsistent PG

[Wesley Dillingham]

In case it's not obvious I forgot a space: "rados list-inconsistent-obj
15.f4f"

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Tue, Oct 10, 2023 at 4:55 PM Wesley Dillingham 
wrote:

> You likely have a failing disk, what does "rados
> list-inconsistent-obj15.f4f" return?
>
> It should identify the failing osd. Assuming "ceph osd ok-to-stop "
> returns in the affirmative for that osd, you likely need to stop the
> associated osd daemon, then mark it out "ceph osd out  wait for it
> to backfill the inconsistent PG and then re-issue the repair. Then turn to
> replacing the disk.
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Tue, Oct 10, 2023 at 4:46 PM  wrote:
>
>> Hello All,
>> Greetings. We've a Ceph Cluster with the version
>> *ceph version 14.2.16-402-g7d47dbaf4d
>> (7d47dbaf4d0960a2e910628360ae36def84ed913) nautilus (stable)
>>
>>
>> ===
>>
>> Issues: 1 pg in inconsistent state and does not recover.
>>
>> # ceph -s
>>   cluster:
>> id: 30d6f7ee-fa02-4ab3-8a09-9321c8002794
>> health: HEALTH_ERR
>> 2 large omap objects
>> 1 pools have many more objects per pg than average
>> 159224 scrub errors
>> Possible data damage: 1 pg inconsistent
>> 2 pgs not deep-scrubbed in time
>> 2 pgs not scrubbed in time
>>
>> # ceph health detail
>>
>> HEALTH_ERR 2 large omap objects; 1 pools have many more objects per pg
>> than average; 159224 scrub errors; Possible data damage: 1 pg inconsistent;
>> 2 pgs not deep-scrubbed in time; 2 pgs not scrubbed in time
>> LARGE_OMAP_OBJECTS 2 large omap objects
>> 2 large objects found in pool 'default.rgw.log'
>> Search the cluster log for 'Large omap object found' for more details.
>> MANY_OBJECTS_PER_PG 1 pools have many more objects per pg than average
>> pool iscsi-images objects per pg (541376) is more than 14.9829 times
>> cluster average (36133)
>> OSD_SCRUB_ERRORS 159224 scrub errors
>> PG_DAMAGED Possible data damage: 1 pg inconsistent
>> pg 15.f4f is active+clean+inconsistent, acting
>> [238,106,402,266,374,498,590,627,684,73,66]
>> PG_NOT_DEEP_SCRUBBED 2 pgs not deep-scrubbed in time
>> pg 1.5c not deep-scrubbed since 2021-04-05 23:20:13.714446
>> pg 1.55 not deep-scrubbed since 2021-04-11 07:12:37.185074
>> PG_NOT_SCRUBBED 2 pgs not scrubbed in time
>> pg 1.5c not scrubbed since 2023-07-10 21:15:50.352848
>> pg 1.55 not scrubbed since 2023-06-24 10:02:10.038311
>>
>> ==
>>
>>
>> We have implemented below command to resolve it
>>
>> 1. We have ran pg repair command "ceph pg repair 15.f4f
>> 2. We have restarted associated  OSDs that is mapped to pg 15.f4f
>> 3. We tuned osd_max_scrubs value and set it to 9.
>> 4. We have done scrub and deep scrub by ceph pg scrub 15.4f4 & ceph pg
>> deep-scrub 15.f4f
>> 5. We also tried to ceph-objectstore-tool command to fix it
>> ==
>>
>> We have checked the logs of the primary OSD of the respective
>> inconsistent PG and found the below errors.
>> [ERR] : 15.f4fs0 shard 402(2)
>> 15:f2f3fff4:::94a51ddb-a94f-47bc-9068-509e8c09af9a.7862003.20_c%2f4%2fd61%2f885%2f49627697%2f192_1.ts:head
>> : missing
>> /var/log/ceph/ceph-osd.238.log:339:2023-10-06 00:37:06.410 7f65024cb700
>> -1 log_channel(cluster) log [ERR] : 15.f4fs0 shard 266(3)
>> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
>> : missing
>> /var/log/ceph/ceph-osd.238.log:340:2023-10-06 00:37:06.410 7f65024cb700
>> -1 log_channel(cluster) log [ERR] : 15.f4fs0 shard 402(2)
>> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
>> : missing
>> /var/log/ceph/ceph-osd.238.log:341:2023-10-06 00:37:06.410 7f65024cb700
>> -1 log_channel(cluster) log [ERR] : 15.f4fs0 shard 590(6)
>> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
>> : missing
>> ===
>> and also we noticed that the no. of

[ceph-users] Re: Unable to fix 1 Inconsistent PG

[Wesley Dillingham]

You likely have a failing disk, what does "rados
list-inconsistent-obj15.f4f" return?

It should identify the failing osd. Assuming "ceph osd ok-to-stop "
returns in the affirmative for that osd, you likely need to stop the
associated osd daemon, then mark it out "ceph osd out  wait for it
to backfill the inconsistent PG and then re-issue the repair. Then turn to
replacing the disk.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, Oct 10, 2023 at 4:46 PM  wrote:

> Hello All,
> Greetings. We've a Ceph Cluster with the version
> *ceph version 14.2.16-402-g7d47dbaf4d
> (7d47dbaf4d0960a2e910628360ae36def84ed913) nautilus (stable)
>
>
> ===
>
> Issues: 1 pg in inconsistent state and does not recover.
>
> # ceph -s
>   cluster:
> id: 30d6f7ee-fa02-4ab3-8a09-9321c8002794
> health: HEALTH_ERR
> 2 large omap objects
> 1 pools have many more objects per pg than average
> 159224 scrub errors
> Possible data damage: 1 pg inconsistent
> 2 pgs not deep-scrubbed in time
> 2 pgs not scrubbed in time
>
> # ceph health detail
>
> HEALTH_ERR 2 large omap objects; 1 pools have many more objects per pg
> than average; 159224 scrub errors; Possible data damage: 1 pg inconsistent;
> 2 pgs not deep-scrubbed in time; 2 pgs not scrubbed in time
> LARGE_OMAP_OBJECTS 2 large omap objects
> 2 large objects found in pool 'default.rgw.log'
> Search the cluster log for 'Large omap object found' for more details.
> MANY_OBJECTS_PER_PG 1 pools have many more objects per pg than average
> pool iscsi-images objects per pg (541376) is more than 14.9829 times
> cluster average (36133)
> OSD_SCRUB_ERRORS 159224 scrub errors
> PG_DAMAGED Possible data damage: 1 pg inconsistent
> pg 15.f4f is active+clean+inconsistent, acting
> [238,106,402,266,374,498,590,627,684,73,66]
> PG_NOT_DEEP_SCRUBBED 2 pgs not deep-scrubbed in time
> pg 1.5c not deep-scrubbed since 2021-04-05 23:20:13.714446
> pg 1.55 not deep-scrubbed since 2021-04-11 07:12:37.185074
> PG_NOT_SCRUBBED 2 pgs not scrubbed in time
> pg 1.5c not scrubbed since 2023-07-10 21:15:50.352848
> pg 1.55 not scrubbed since 2023-06-24 10:02:10.038311
>
> ==
>
>
> We have implemented below command to resolve it
>
> 1. We have ran pg repair command "ceph pg repair 15.f4f
> 2. We have restarted associated  OSDs that is mapped to pg 15.f4f
> 3. We tuned osd_max_scrubs value and set it to 9.
> 4. We have done scrub and deep scrub by ceph pg scrub 15.4f4 & ceph pg
> deep-scrub 15.f4f
> 5. We also tried to ceph-objectstore-tool command to fix it
> ==
>
> We have checked the logs of the primary OSD of the respective inconsistent
> PG and found the below errors.
> [ERR] : 15.f4fs0 shard 402(2)
> 15:f2f3fff4:::94a51ddb-a94f-47bc-9068-509e8c09af9a.7862003.20_c%2f4%2fd61%2f885%2f49627697%2f192_1.ts:head
> : missing
> /var/log/ceph/ceph-osd.238.log:339:2023-10-06 00:37:06.410 7f65024cb700 -1
> log_channel(cluster) log [ERR] : 15.f4fs0 shard 266(3)
> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
> : missing
> /var/log/ceph/ceph-osd.238.log:340:2023-10-06 00:37:06.410 7f65024cb700 -1
> log_channel(cluster) log [ERR] : 15.f4fs0 shard 402(2)
> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
> : missing
> /var/log/ceph/ceph-osd.238.log:341:2023-10-06 00:37:06.410 7f65024cb700 -1
> log_channel(cluster) log [ERR] : 15.f4fs0 shard 590(6)
> 15:f2f2:::94a51ddb-a94f-47bc-9068-509e8c09af9a.11432468.3_TN8QHE_04.20.2020_08.41%2fCV_MAGNETIC%2fV_274396%2fCHUNK_2440801%2fSFILE_CONTAINER_031.FOLDER%2f3:head
> : missing
> ===
> and also we noticed that the no. of scrub errors in ceph health status are
> matching with the ERR log entries in the primary OSD logs of the
> inconsistent PG as below
> grep -Hn 'ERR' /var/log/ceph/ceph-osd.238.log|wc -l
> 159226
> 
> Ceph is cleaning the scrub errors but rate of scrub repair is very slow
> (avg of 200 scrub errors per day) ,we want to increase the rate of scrub
> error repair to finish the cleanup of pending 159224 scrub errors.
>
> #ceph pg 15.f4f query
>
>
> {
> "state": "active+clean+inconsistent",
> "snap_trimq": "[]",
> "snap_trimq_len": 0,
> "epoch": 409009,
> "up": [
> 238,
> 106,
> 402,
> 266,
> 374,
> 498,
> 590,
> 627,
> 684,
> 73,
> 66
> ],
> "acting": [
> 238,
> 106,
> 402,
> 266,
> 374,
> 498,
> 590,
> 627,

Re: Syntax of Perl

[wesley]

I would say perl syntax is similar to ruby and scalar.
https://tech.postno.de/archives/113

regards.



> 
> The syntax of Perl have similarity with Python.
> 
> -- 
> 
> With kindest regards, William.
> 
> ⢀⣴⠾⠻⢶⣦⠀ 
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org https://www.debian.org/ 
> ⠈⠳⣄
>

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

Re: Perl version 5.8 and 5.10

[wesley]

my perl version shipped by ubuntu 22.04 is 5.34.0.

This is perl 5, version 34, subversion 0 (v5.34.0) built for 
x86_64-linux-gnu-thread-multi

regards.


> 
> Hello, 
> 
> What's the motivation to install a version which is 21 years old ?
> 
> If you have an old code probably is better try to update it. 
> 
> Best Regards,
> 
> Armando
> 
> 
> 
> **From:** Kang-min Liu 
> **Sent:** Sunday, October 8, 2023 5:32:24 AM
> **To:** beginners@perl.org 
> **Subject:** Re: Perl version 5.8 and 5.10
>  
> 
> 於 2023年10月8日 上午11:53:46 [GMT+09:00]，William Torrez Corea 
>  寫到：
> 
> > 
> > I Tried to install perl version 5.8 and 5.10 with perlbrew but i can't 
> > install this version.
> > 
> > I get the following error message:
> > 
> > > 
> > > 50 tests and 269 subtests skipped.
> > > make[2]: *** [makefile:701: _test_tty] Error 29
> > > make[2]: Leaving directory 'perl5/perlbrew/build/perl-5.8.0/perl-5.8.0'
> > > make[1]: *** [makefile:709: _test] Error 2
> > > make[1]: Leaving directory 'perl5/perlbrew/build/perl-5.8.0/perl-5.8.0'
> > > make: *** [makefile:779: test_harness] Error 2
> > > # Brew Failed #
> > >
> > 
> 
> Generally speaking, building old software on a newer system is going to yield 
> warnings / errors that are introduced latter then the release of the 
> software
> 
> That said,  those errors seem to be about unit tests rather than 
> comiplation.You may be able to cd into the build dir and still run a `make 
> install` to finish the installation, if you are willing to just ignore those 
> errors. If those are all the errors in the lot, I imagine that most of the 
> perl-5.8.0 would still work.
> 
> --
> Kang-min Liu
>

--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/

[RBW] Re: Carrying groceries on your bike

[Wesley]

Include me in the pannier party. Once I felt I had reached the limit of 
safe riding with a Costco run (low-speed shimmies, though everything was 
smooth and stable at "speed".) Got home and weighed the load, it was 55 
pounds. Rear rack only, Ortlieb "city" panniers.
-Wes

On Thursday, October 5, 2023 at 6:28:42 PM UTC-7 Paul in Dallas wrote:

>
>
> I know this probably has been discussed before.
>
> If you use your bike for such errands what is your method of transporting 
> groceries or other items?
>
> I have one bike with a rack and a large Wald basket that can handle a 
> couple bags of groceries but sometimes as I rotate through my bikes I use 
> the method pictured below of tying cloth sacks around the handlebar 
> balancing the load.
>
> I think this can be a risky method.
>
> I need to find some decent grocery panniers.
>
> Today I weighed these 2 sacks in bathroom scales.
>
> Dang...36.2 pounds. Glad it was only 2 miles return trip .
>
> Paul in Dallas
>
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/681707d5-aa9d-4903-94de-5a8d14f92a41n%40googlegroups.com.

[ceph-users] Re: cannot repair a handful of damaged pg's

[Wesley Dillingham]

A repair is just a type of scrub and it is also limited by osd_max_scrubs
which in pacific is 1.

If another scrub is occurring on any OSD in the PG it wont start.

do "ceph osd set noscrub" and "ceph osd set nodeep-scrub" wait for all
scrubs to stop (a few seconds probably)

Then issue the pg repair command again. It may start.

You also have pgs in backfilling state. Note that by default OSDs in
backfill or backfill_wait also wont perform scrubs.

You can modify this behavior with `ceph config set osd
osd_scrub_during_recovery
true`

I would suggest only setting that after the noscub flags are set and the
only scrub you want to get processed is your manual repair.

Then rm the scrub_during_recovery config item before unsetting the noscrub
flags.



Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Fri, Oct 6, 2023 at 11:02 AM Simon Oosthoek 
wrote:

> On 06/10/2023 16:09, Simon Oosthoek wrote:
> > Hi
> >
> > we're still in HEALTH_ERR state with our cluster, this is the top of the
> > output of `ceph health detail`
> >
> > HEALTH_ERR 1/846829349 objects unfound (0.000%); 248 scrub errors;
> > Possible data damage: 1 pg recovery_unfound, 2 pgs inconsistent;
> > Degraded data redundancy: 6/7118781559 objects degraded (0.000%), 1 pg
> > degraded, 1 pg undersized; 63 pgs not deep-scrubbed in time; 657 pgs not
> > scrubbed in time
> > [WRN] OBJECT_UNFOUND: 1/846829349 objects unfound (0.000%)
> >  pg 26.323 has 1 unfound objects
> > [ERR] OSD_SCRUB_ERRORS: 248 scrub errors
> > [ERR] PG_DAMAGED: Possible data damage: 1 pg recovery_unfound, 2 pgs
> > inconsistent
> >  pg 26.323 is active+recovery_unfound+degraded+remapped, acting
> > [92,109,116,70,158,128,243,189,256], 1 unfound
> >  pg 26.337 is active+clean+inconsistent, acting
> > [139,137,48,126,165,89,237,199,189]
> >  pg 26.3e2 is active+clean+inconsistent, acting
> > [12,27,24,234,195,173,98,32,35]
> > [WRN] PG_DEGRADED: Degraded data redundancy: 6/7118781559 objects
> > degraded (0.000%), 1 pg degraded, 1 pg undersized
> >  pg 13.3a5 is stuck undersized for 4m, current state
> > active+undersized+remapped+backfilling, last acting
> > [2,45,32,62,2147483647,55,116,25,225,202,240]
> >  pg 26.323 is active+recovery_unfound+degraded+remapped, acting
> > [92,109,116,70,158,128,243,189,256], 1 unfound
> >
> >
> > For the PG_DAMAGED pgs I try the usual `ceph pg repair 26.323` etc.,
> > however it fails to get resolved.
> >
> > The osd.116 is already marked out and is beginning to get empty. I've
> > tried restarting the osd processes of the first osd listed for each PG,
> > but that doesn't get it resolved either.
> >
> > I guess we should have enough redundancy to get the correct data back,
> > but how can I tell ceph to fix it in order to get back to a healthy
> state?
>
> I guess this could be related to the number of scrubs going on, I read
> somewhere that this may interfere with the repair request. I would
> expect the repair would have priority over scrubs...
>
> BTW, we're running pacific for now, we want to update when the cluster
> is healthy again.
>
> Cheers
>
> /Simon
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[kwin] [Bug 475062] Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

--- Comment #3 from Wesley M  ---
Created attachment 162067
  --> https://bugs.kde.org/attachment.cgi?id=162067=edit
kwinrc as of Oct 3 2023

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475062] Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

--- Comment #2 from Wesley M  ---
Sure thing. I'll both attach it and copy/paste the contents.

[$Version]
update_info=kwin.upd:replace-scalein-with-scale,kwin.upd:port-minimizeanimation-effect-to-js,kwin.upd:port-scale-effect-to-js,kwin.upd:port-dimscreen-effect-to-js,kwin.upd:auto-bordersize,kwin.upd:animation-speed,kwin.upd:desktop-grid-click-behavior,kwin.upd:no-swap-encourage,kwin.upd:make-translucency-effect-disabled-by-default,kwin.upd:remove-flip-switch-effect,kwin.upd:remove-cover-switch-effect,kwin.upd:remove-cubeslide-effect,kwin.upd:remove-xrender-backend,kwin.upd:enable-scale-effect-by-default,kwin.upd:overview-group-plugin-id,kwin.upd:animation-speed-cleanup,kwin.upd:replace-cascaded-zerocornered

[Compositing]
AllowTearing=false
LatencyPolicy=High

[Desktops]
Id_1=fc3c7e5b-abd4-4f4f-8028-9221ca45
Id_2=cc3d503b-33c0-4ea4-817f-1598012a4935
Id_3=8201614b-d4c0-4e17-bdc0-74c096876eb0
Name_1=1
Name_2=2
Name_3=3
Number=3
Rows=3

[Effect-kwin4_effect_animationsSuite]
minimizeEffect=43
unminimizeEffect=35

[Effect-windowview]
BorderActivateAll=9

[Input]
TabletMode=off

[NightColor]
Active=true
LatitudeFixed=34.29
LongitudeFixed=-77.85
Mode=Location
NightTemperature=2400

[Plugins]
TIL3REnabled=false
auto-tiling-customEnabled=false
autotileEnabled=false
blurEnabled=true
contrastEnabled=false
even-better-quick-tilesEnabled=false
exquisiteEnabled=false
flexGridEnabled=false
forceblurEnabled=false
karouselEnabled=false
krohnkiteEnabled=false
ktileEnabled=false
kwin-wranglerEnabled=false
kwin4_effect_dimscreenEnabled=true
kwin4_effect_rubberband_maximizeEnabled=false
kwin4_effect_scaleEnabled=false
kwin4_effect_translucencyEnabled=true
kwin4_effect_tvEnabled=true
kzonesEnabled=false
maximizetotileEnabled=false
overviewEnabled=false
poloniumEnabled=false
quarter-tilingEnabled=false
quick-tile-2Enabled=false
quicktile-enhancementsEnabled=false
screenedgeEnabled=false
sheetEnabled=true
truely-maximizedEnabled=false
windowviewEnabled=false
zoomEnabled=false

[Script-autotile]
InvertInsertion=false
KeepTiledBelow=false
UseWhitelist=true

[Script-exquisite]
columns=4

[Script-karousel]
untileOnDrag=false

[Script-polonium]
DefaultEngine=4
KeepTiledBelow=false
MaximizeSingle=true
Unfullscreen=true

[TabBox]
OrderMinimizedMode=1
ShowTabBox=false

[Tiling]
padding=4

[Tiling][4fd2297f-4641-507d-9450-e87395b4b2d5]
tiles={"layoutDirection":"horizontal","tiles":[{"width":0.5},{"width":0.5}]}

[Tiling][c290b9e9-3829-5319-aad9-4bad5823e26b]
tiles={"layoutDirection":"vertical","tiles":[{"height":0.5},{"height":0.5}]}

[Tiling][c57e74c8-c957-5a0a-a51b-f2dff0ddbf51]
tiles={"layoutDirection":"horizontal","tiles":[{"width":0.5},{"width":0.5}]}

[Tiling][d02c035d-eef0-5c68-aa2f-2e83d0ba08b1]
tiles={"layoutDirection":"horizontal","tiles":[{"width":0.25},{"width":0.5},{"width":0.25}]}

[Wayland]
EnablePrimarySelection=false

[Windows]
BorderSnapZone=20
ElectricBorderMaximize=false
MaximizeButtonMiddleClickCommand=Maximize
MaximizeButtonRightClickCommand=Maximize
SeparateScreenFocus=true
TitlebarDoubleClickCommand=Nothing

[Xwayland]
Scale=1

[org.kde.kdecoration2]
ButtonsOnLeft=XAI
ButtonsOnRight=HMS
library=org.kde.breeze
theme=Breeze

-- 
You are receiving this mail because:
You are watching all bug changes.

Re: [RBW] Re: What shoes does your Riv wear?

[Wesley]

In fact, I think it was Grant (or maybe Sheldon Brown?) who turned me onto 
the idea that wide tires are great, especially when they're NOT knobby. For 
the past 15 years, it's been Panaracer Paselas for my road bike and 
Schwalbe Big Apple/Fat Frank for my commute/errand bike. The idea that 
there are noticeable gains to be had from tubeless or RH tires seems like 
pure hype to me, but I may be wrong. Certainly the Schwalbe tires are crazy 
heavy and that must affect my acceleration. But once I'm up to speed, I 
doubt it matters.
-Wes

On Tuesday, October 3, 2023 at 8:41:57 AM UTC-7 Jeremy Till wrote:

> I doubt that Grant was intentionally designing his bikes specifically to 
> handle better with knobbier tires. I think it's more a product of his own 
> views of how a bike should handle and the tires that were available/common 
> at the time he designed the bike. On the first point, he's written a few 
> times defending the virtues of geometric trail, perhaps as a response to 
> challenges from Jan-Heine-o-philes who wanted him to design a low trail 
> bike. On the second point, most of the tires we're discussing were nothing 
> but a twinkle in Jan Heine or Panaracer's eyes when the Rambouillet was 
> designed, and I think it probably handles best with 28-32mm road tires 
> because that was considered downright obese for a road bike at the time. 
> For the Clem, certainly that was designed closer to the contemporary golden 
> age of fat tires, but I still remember most of the prototypes wearing 
> something like a Schwalbe Big Ben, which has more of a blockier tread that 
> probably reduces pneumatic trail compared to something like an RH slick. 
>
> Jeremy Till 
> Sacramento, CA
>
> On Monday, October 2, 2023 at 6:46:34 PM UTC-7 ted.l...@gmail.com wrote:
>
>> Jeremy,
>>
>> You make a good point about the geometric and pneumatic trail and the 
>> possibility that Grant designed his frames around a knobbier, more general 
>> purpose, tire thus building the frames with more geometric trail. I’d love 
>> to ask Grant that question to know if it was happy coincidence that they 
>> ended up that way or if the design choice was really that intentional.
>>
>> On Mon, Oct 2, 2023 at 4:22 PM Jeremy Till  wrote:
>>
>>> On my Rivendells I've noticed that, irrespective of the surface I'm 
>>> riding on, I actually prefer the handling with larger knobby tires than 
>>> with larger slick tires. This is true on both my Clem H (2016, first-gen) 
>>> with 45-55mm tires and my Rambouillet (green, ~2006 as far as I can tell) 
>>> with 36-38mm tires. My explanation for this is that Grant tends to design 
>>> bikes with larger geometric trail. When you add in the pneumatic trail of 
>>> larger slick tires, the whole thing can feel harder to turn. Knobby tires 
>>> give you the same shock absorption while putting less rubber on the 
>>> pavement, thus reducing the pneumatic trail. Jan Heine has noted this 
>>> effect himself when comparing knobby and slick versions of his tires. 
>>>
>>> My Rambouillet current wears RH (actually Compass, they're a few years 
>>> old) Steilacoom 700x38 knobbies. My Clem H has 29x2.2 Specialized Fast 
>>> Traks with the "Control" casing, which is an XC-oriented MTB tire with 
>>> relatively minimal knobs that rolls well on pavement. In my experience 
>>> there is no free lunch when it comes to supple casings and flats. Certainly 
>>> the ride is better with things like the RH standard casing but my rate of 
>>> flatting from glass and thorns goes up. Sealant and tubeless haven't been 
>>> the solution, in my experience, and I run both of my Rivendells with 
>>> tubes.  
>>>
>>> Since Patrick was also mentioning them I will say that I've used both 
>>> the 700x42 and 700x38 versions of the Soma Supple Vitesse EX on my Long 
>>> Haul Trucker, which seems to handle better with large slicks than my 
>>> Rivendells. Those are good tires with an acceptable flat rate for me. I 
>>> also tried the 700x38 SL version on my Rambouillet and found that not only 
>>> did I not like the handling, but the flat rate was excessive for me. Note 
>>> that the only difference between the EX and SL Supple Vitesses is the 
>>> thickness of the tread, with the EX having thicker treads. Unlike RH and 
>>> other brands there is no difference in the casing between the lightweight 
>>> and longer wearing versions. I believe that the Shikiro is the same tread 
>>> as the Supple Vitesse EX with a heavier duty casing.  
>>>
>>> Jeremy Till
>>> Sacramento, CA
>>>
>>> On Monday, October 2, 2023 at 8:26:17 AM UTC-7 ted.l...@gmail.com wrote:
>>>
 I’ve had tires on the brain this last week. I was thinking I might want 
 to try something a little narrower on my Appaloosa so I’ve been a bit 
 absorbed with that thought.

 At the moment I run the SimWorks Super Yummy tire with the black 
 sidewall in 29x2.25”. I previously had their 26x2.25” tan wall tires on a 
 26” build and absolutely loved them on 

Re: [RBW] Re: Best mitten design for very cold weather

[Wesley]

Honestly, Bar Mitts brand neoprene pogies are so amazing that I would 
recommend just buying enough pairs that you can put them on each bike. Or 
swapping one pair between bikes as necessary (that can be complicated on 
the drop-bar version, depending on your cable routing). They are far beyond 
any gloves or mittens worn on the hands because they block the cold wind 
without being bulky or interfering with your handling the controls. I have 
fingers that are quite cold-sensitive, and I used Bar Mitts for seven years 
of commuting in Wisconsin winters. On the below-zero days I would only have 
to add a pair of minimalist knitted gloves (the kind they sell for 99 cents 
at the supermarket checkout.) 

Bar Mitts rock.
-Wes 

On Tuesday, October 3, 2023 at 8:42:59 AM UTC-7 Patrick Moore wrote:

> Thanks all again. Now the problem is, there are too many damned choices. 
> My first choice would be that Gander hunters' mitten with the flip-back 
> finger cover but I can't find it online. I'll have to review the other 
> choices again, but right now (probably because I just looked at it) I'm 
> leaning at 45* toward the LLBean Goretex Primaloft mitten because, well 
> because I just looked at it, but also because it's got a bit of a gauntlet 
> but not elbow-length, and it has positive reviews from a Canadian winter 
> runner and (unless he was being sarcastic) someone who said he wore it 
> comfortably in Antartica. And it's only $70, *and *I've meant to try 
> LLBean again after decades; I used to be a good customer.
>
> Hand warmers: thanks for the suggestion, but my very cold weather rides 
> tend to be brief, if only because at 5K feet, once the sun comes up the 
> temperatures also shoot up. So an easy-on/easy off mitten with a wool 
> underglove is a good system for my riding.
>
> I'll have some winter gear for sale shortly: Very nice but slightly too 
> short Wabi Woolens LS jersey professionally and excellently retrofitted 
> with a full-length zipper; a Varusteleka heavy full-zip, high-neck sweater 
> with thumb holes but too heavy for my needs; and some Large little used PI 
> lobster mitts. Watch this space.
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/b8c6b2fa-1790-4899-bfff-d8a4c4e63dffn%40googlegroups.com.

[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475064

--- Comment #3 from Wesley M  ---
Created attachment 161980
  --> https://bugs.kde.org/attachment.cgi?id=161980=edit
Display Update Fix

This shows where I updated the display, which fixed the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475064

--- Comment #2 from Wesley M  ---
Created attachment 161979
  --> https://bugs.kde.org/attachment.cgi?id=161979=edit
Wallpaper Change Test

This shows a test where I changed the wallpaper. This did not affect the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475064

--- Comment #1 from Wesley M  ---
Created attachment 161978
  --> https://bugs.kde.org/attachment.cgi?id=161978=edit
Video Example

This shows the bug after it spontaneously occurred.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475064] New: Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475064

Bug ID: 475064
   Summary: Compositing or Virtual Screenspace Issue -  Maybe
wallpaper and display resolution mismatch?
Classification: Plasma
   Product: kwin
   Version: 5.27.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wmprivacyem...@gmail.com
  Target Milestone: ---

SUMMARY
***
Wallpaper will sometimes resize on its own to a resolution smaller than the
display is running, causing strange graphical glitches until the display is
updated (move or resized) in the settings.
***


STEPS TO REPRODUCE
1. Unknown. Happens without warning. 

OBSERVED RESULT
It...happens?

EXPECTED RESULT
It shouldn't.

SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
n/a

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475063] New: Wishlist - Custom Tiling - Snap back to tiled position after unmaximizing.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475063

Bug ID: 475063
   Summary: Wishlist - Custom Tiling - Snap back to tiled position
after unmaximizing.
Classification: Plasma
   Product: kwin
   Version: 5.27.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Custom Tiling
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wmprivacyem...@gmail.com
CC: notm...@gmail.com
  Target Milestone: ---

SUMMARY
***
Wishlist - Custom Tiling - Snap back to tiled position after unmaximizing.
***


STEPS TO REPRODUCE
1. Tile a window to a defined space by holding shift while dragging the window.
2. Maximize the window.
3. Unmaximize the window.

OBSERVED RESULT
The window reverts to a floating state.

EXPECTED RESULT
Unless it is dragged/etc., the window should snap back to its tiled position
after being unmaximized.

SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
n/a

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 475062] New: Maximized flag not updated when window is dragged.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475062

Bug ID: 475062
   Summary: Maximized flag not updated when window is dragged.
Classification: Plasma
   Product: kwin
   Version: 5.27.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: wmprivacyem...@gmail.com
  Target Milestone: ---

Created attachment 161976
  --> https://bugs.kde.org/attachment.cgi?id=161976=edit
Video Example

SUMMARY
***
Maximized flag not updated when window is dragged.
***


STEPS TO REPRODUCE
1. Maximize any window.
2. Using the titlebar or the super key, drag the window.

OBSERVED RESULT
The window keeps its size, shape, and maximized status, but moves with the drag
operation.

EXPECTED RESULT
The window should no longer be maximized. It should revert to it's floating
size and shape, but still change position to match the dragging operation.

SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
n/a

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 475061] New: System Settings ignoring failsafe timeout if window is closed before time expires.

[Wesley M]

https://bugs.kde.org/show_bug.cgi?id=475061

Bug ID: 475061
   Summary: System Settings ignoring failsafe timeout if window is
closed before time expires.
Classification: Applications
   Product: systemsettings
   Version: 5.27.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_kscreen
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: wmprivacyem...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 161975
  --> https://bugs.kde.org/attachment.cgi?id=161975=edit
Video Example

SUMMARY
***
System Settings ignoring failsafe timeout if window is closed before time
expires.
***


STEPS TO REPRODUCE
1. Open display settings.
2. Adjust a setting that uses a timeout failsafe to revert changes if the
applied changes break the system and the user is unable to interact with
settings window within the timeout period.
3. Close the display settings window before the timeout period expires.

OBSERVED RESULT
When the window is closed, the changes appear to be permanently saved.

EXPECTED RESULT
The changes should be reverted, as the user did not approve the applied changes
during the failsafe timeout period. If the window is accidentally closed,
crashes, the desktop environment restarts, or the system is shut down; then it
should revert to the last known-good settings, instead of potentially trapping
the user in a misconfigured or unusable system.

SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Note that the video example shows a different issue with OBS recording the
cursor position incorrectly after the resolution change. It is unrelated to
this bug report. However, it can be used to show the resolution was changed and
did not revert after the window closed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[pkg-go] Bug#1052449: podman: add pasta(passt) as dependency

[Wesley H. Gimenes]

Package: podman
Version: 4.6.2+ds1-2
Severity: normal
X-Debbugs-Cc: wehagy+deb...@gmail.com


Dear Maintainer,

Upstream podman-v4.4+ have added support to a new rootless networking mode 
called 
pasta(package name is passt), but the package is not added as dependency
for podman on debian, I think is a good ideia add pasta(passt) as a
recommends package like slirp4netns.

Steps to reproduce:

1. Install podman
:~$ sudo apt install podman -y

2. Run nginx container as rootless user and expose on port 8080 on host,
   pasta(passt) only works as rootless, see "--nerwork pasta"
:~$ podman run --rm --detach --publish 8080:80 --network pasta docker.io/nginx
Error: could not find pasta, the network namespace can't be configured: exec: 
"pasta": executable file not found in $PATH

3. Fix, install pasta(passt)
:~$ sudo apt install passt -y

4. Repeat step 4
:~$ podman run --rm --detach --publish 8080:80 --nertwork pasta docker.io/nginx
1f8727e9785131431d2d91b043784dd8451b54e4542617eb7270a5d8176912a1

5. No error, and nginx is running fine
:~$ curl localhost:8080



Welcome to nginx!

html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }



Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
http://nginx.org/;>nginx.org.
Commercial support is available at
http://nginx.com/;>nginx.com.

Thank you for using nginx.




Thanks
Wesley H. Gimenes


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.12-200.fc38.x86_64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages podman depends on:
ii  conmon   2.1.6+ds1-1
ii  crun 1.9-1
ii  golang-github-containers-common  0.55.4+ds1-3
ii  libc62.37-10
ii  libdevmapper1.02.1   2:1.02.185-2
ii  libgpgme11   1.18.0-3+b1
ii  libseccomp2  2.5.4-1+b3
ii  libsqlite3-0 3.43.1-1
ii  libsubid41:4.13+dfsg1-1+b1

Versions of packages podman recommends:
ii  buildah1.31.2+ds1-3
ii  catatonit  0.1.7-1+b1
ii  dbus-user-session  1.14.10-1
ii  slirp4netns1.2.1-1
ii  uidmap 1:4.13+dfsg1-1+b1

Versions of packages podman suggests:
pn  containers-storage  
pn  docker-compose  
ii  fuse-overlayfs  1.10-1
ii  iptables1.8.9-2

-- no debconf information

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

Bug#1052449: podman: add pasta(passt) as dependency

[Wesley H. Gimenes]

Package: podman
Version: 4.6.2+ds1-2
Severity: normal
X-Debbugs-Cc: wehagy+deb...@gmail.com


Dear Maintainer,

Upstream podman-v4.4+ have added support to a new rootless networking mode 
called 
pasta(package name is passt), but the package is not added as dependency
for podman on debian, I think is a good ideia add pasta(passt) as a
recommends package like slirp4netns.

Steps to reproduce:

1. Install podman
:~$ sudo apt install podman -y

2. Run nginx container as rootless user and expose on port 8080 on host,
   pasta(passt) only works as rootless, see "--nerwork pasta"
:~$ podman run --rm --detach --publish 8080:80 --network pasta docker.io/nginx
Error: could not find pasta, the network namespace can't be configured: exec: 
"pasta": executable file not found in $PATH

3. Fix, install pasta(passt)
:~$ sudo apt install passt -y

4. Repeat step 4
:~$ podman run --rm --detach --publish 8080:80 --nertwork pasta docker.io/nginx
1f8727e9785131431d2d91b043784dd8451b54e4542617eb7270a5d8176912a1

5. No error, and nginx is running fine
:~$ curl localhost:8080



Welcome to nginx!

html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }



Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
http://nginx.org/;>nginx.org.
Commercial support is available at
http://nginx.com/;>nginx.com.

Thank you for using nginx.




Thanks
Wesley H. Gimenes


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.12-200.fc38.x86_64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages podman depends on:
ii  conmon   2.1.6+ds1-1
ii  crun 1.9-1
ii  golang-github-containers-common  0.55.4+ds1-3
ii  libc62.37-10
ii  libdevmapper1.02.1   2:1.02.185-2
ii  libgpgme11   1.18.0-3+b1
ii  libseccomp2  2.5.4-1+b3
ii  libsqlite3-0 3.43.1-1
ii  libsubid41:4.13+dfsg1-1+b1

Versions of packages podman recommends:
ii  buildah1.31.2+ds1-3
ii  catatonit  0.1.7-1+b1
ii  dbus-user-session  1.14.10-1
ii  slirp4netns1.2.1-1
ii  uidmap 1:4.13+dfsg1-1+b1

Versions of packages podman suggests:
pn  containers-storage  
pn  docker-compose  
ii  fuse-overlayfs  1.10-1
ii  iptables1.8.9-2

-- no debconf information

[RBW] Re: Help me repair Pam's Silver shifters

[Wesley]

I am frankly amazed at the workout Pam is giving her bike, to wear out 
multiple shifter pawls! I can imagine a few ways to do a repair, none of 
which are "worth it", in terms of resource and money cost (3D printing, 
filing down a bit of aluminum bar, CNC milling). The most expedient fix, 
IMO, would be to epoxy the ratchet gear to the shifter body so that the 
both directions work in friction mode.
-Wes

On Tuesday, September 19, 2023 at 8:02:06 PM UTC-7 eric...@gmail.com wrote:

> Hi all — I'm looking for some neglected, cast off or broken Silver 1 
> shifters to scavenge so that I can repair some broken Silver 1 shifters 
> sent to me by forum member Pam Murray. If you have some you aren't using or 
> that you think are broken which you are willing to send me for the cost of 
> shipping please let me know. I will use them to repair Pam's shifters and 
> get them back to her! 
>
> I recently read enjoyed Pam's thread on broken Silver shifters 
> . 
> And right on time one of my Silvers broke. So I took mine apart to have a 
> look. It turns out the spring was clogged with corrosion and wouldn't 
> compress, allowing for the pawl to hold the ratchet wheel and hold tension 
> on the shifter cable. Luckily the spring and pawl only needed to be cleaned 
> and reassembled. 
>
> Pam sent me three broken Silver shifters. As many of us know, Pam has put 
> tens of thousands of miles on her legendary Betty Foy. She's worn out many 
> parts and she's interested in getting them back into service when possible. 
> I took a look and was able to fix one of the shifters. The other two 
> require new pawls, which I can't locate. 
>
> [image: Screenshot 2023-09-19 at 10.59.05 PM.png]
>
> I reached out to Dia Compe in Taiwan about spare parts. They replied 
> quickly but said they could not send me any bits and pieces and suggested I 
> contact Rivendell. 
>
> So I wrote to Will Keating at Rivendell, who's a wonderfully helpful and 
> nice guy and a friend and he said he'd send me some parts. Well, they 
> arrived today and they're *brand new* Silver 2 levers. I really don't 
> want to destroy brand new shifters to revive old shifters! I'm sure the 
> pawls I need are inside but I can't bring myself to tear them apart. 
> They've very definitely never been installed on a bike. 
>
> I have found some replacement springs from McMaster-Carr 
> . They're heavier gauge wire and 
> slightly longer than the stock springs from Dia Compe. But they fit and 
> they work. They do result in a lever with heavier action but they do not 
> make the lever difficult to operate. 
>
> My plan, once I locate some pawls, is to make a Silver shifter repair and 
> maintenance video. I hope that with donated parts from other members I can 
> fix Pam's shifters, show the process of disassembly, repair and re-assembly 
> and share it with the group (and the rest of the web). I'll include a 
> detailed look of the proper order for all the bits and how the get the 
> shifter closed back up. 
>
> Thanks in advance! 
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/8ea172b2-1168-4e3c-a46f-02f87887a70cn%40googlegroups.com.

[kstars] [Bug 474585] New: Details information is broken and has been since 2019.

[Wesley Handrow]

https://bugs.kde.org/show_bug.cgi?id=474585

Bug ID: 474585
   Summary: Details information is broken and has been since 2019.
Classification: Applications
   Product: kstars
   Version: 3.6.6
  Platform: Other
OS: Other
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: w...@mudlakepottery.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. NOAO no longer exists since 2019. Major of details is broken.
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Enhancements to "ls" and "xattr"

[W. Wesley Groleau (伟思礼)]

It's been at least a decade since I used FreeBSD & Ubuntu regularly, but these 
suggestions I made to Apple apply to any Linux or BSD distro (except maybe for 
#1 which may be Apple-unique)

Below is an excerpt of a directory listing. Suggestions:

(1. Add com.apple.metadata:kMD* to EVERY download, not merely on MP3 files — 
Apple only?)

2. Add an option to "ls -l@" that displays the VALUES of all extended 
attributes instead of their sizes.
(or in addition to size)

3. Add to xattr a way to use wildcards in the name of the extended attribute

4. Add options to xattr and ls to put the fields in the value on separate lines 
instead of semicolon-delimited.
(Even better, interpret the values instead of showing raw)

5. Pass these ideas on to the maintainers of ls & xattr on any other Unix 
variant.


WGroleau@MBP ~ % ls -late@O Downloads | more
total 1735720
-rw-r--r--@ 1 WGroleau staff - 148582 Sep 11 06:31 from_DDG.jpg
com.apple.quarantine 61 
-rw-r--r--@ 1 WGroleau staff - 148582 Sep 11 06:31 from_Safari.jpg
com.apple.quarantine 85 
-rw-r--r--@ 1 WGroleau staff - 219070316 Sep 8 23:06 Sint_Maarten_dload_hi.mp4
com.apple.avkit.thumbnailCacheEncryptionKey 16 
com.apple.avkit.thumbnailCacheIdentifier 16 
com.apple.lastuseddate#PS 16 
com.apple.quarantine 61 
-rw-r--r--@ 1 WGroleau staff - 1497234 Sep 7 07:38 FPB.mp3
com.apple.macl 72 
com.apple.metadata:kMDItemDownloadedDate 53 
com.apple.metadata:kMDItemWhereFroms 154 
com.apple.quarantine 57

--  
Wes Groleau
伟思礼

“If you are offered a free lunch, you are the lunch”

[RBW] Re: Roadini Shifting Problems

[Wesley]

Hi Cat,
Sorry to hear about your frustrations. The last time this happened to me, I 
futzed with it for too long before giving up and replacing the cassette, 
chain rings, and chain all together. That solved it. Just for the record: 
you have replaced the cracked rim, yes?

As for 1x, in my opinion you should keep the front derailer. Maybe just 
don't shift the front for a while (until you're satisfied that everything 
is working properly at the back).
-Wes

On Wednesday, September 6, 2023 at 7:04:57 PM UTC-7 Catherina Gioino wrote:

> Hi RBW group!
>
> My name’s Cat and I posted a few months ago about an earlier iteration of 
> the same problem I’m still having: my Roadini has had trouble shifting both 
> front and rear since I first acquired it over a year ago. I purchased it 
> from the original owner, who had built it up with nice Campy components-- 
> some 
> pictures of the initial setup and the current configuration are below.
>
> It’s set up 2x8, and at first, the front would barely shift to the small 
> ring at all (often not at all), and the chain would pretty frequently jump 
> off if I even lightly overshifted. Then, the rear wheel (Velocity A23) 
> developed a series of large cracks on the rim.
>
> My partner and his dad (who both have Rivs and got me into this mess, 
> haha) tried to fix the problems by first adjusting the limit screws, and 
> when that only made things worse and we discovered the cracked rim, we put 
> on a Shimano cassette, replaced the wheelset with a Shimano-compatible set 
> of A23s, and replaced the chain, on the theory that the original chain was 
> too narrow for the original Campy cassette, letting it slip between the 
> rings. This marginally helped, but still didn’t solve the issues, so then I 
> had my local bike shop put in a wider bottom bracket, because they noticed 
> that the front crank was essentially scraping the front derailleur and 
> couldn’t be adjusted any further— they suggested the bottom bracket 
> replacement.
>
> This didn’t work because on my first real ride post the fixes, (on the OCA 
> coming back from the Tappan Zee for that guy on a Homer who waved!) the 
> front derailleur cage snapped. I was able to ride home, but now I need to 
> at minimum replace my front derailleur, and while I’m at it, would like to 
> fix the larger problems— the rear and front shifting. I love my bike, and 
> tend to ride through issues, but it would be great to be able to shift 
> properly. I’m wondering:
>
> 1) If anyone has any general or specific advice given what I’ve detailed, 
> or any questions that might help diagnose the problem
>
> 2) If anyone in New York would be willing to come take a look at it and 
> try to help figure out the problem— it could be a fun project, and I’m 
> happy to provide refreshments :)
>
> 3) If I do need to switch the entire drivetrain, should I move to a 1x so 
> I don’t run into more front derailleur problems? I tend to ride mostly in 
> my higher gears anyway, so I could just move to a 1x with a wider-range 
> cassette and stick with my 44 in front. I know 1x can come with its own 
> issues, but this might be easier
>
> 4) I’m Italian, and so I have a slight but unavoidable aesthetic 
> preference for sticking with Campy parts; does anyone have thoughts about 
> how I might do this, or should I give up and switch to more standard 
> Shimano or SRAM, which won’t look as nice but might function better
>
> Thanks so much for reading and for any help or advice! I’m kind of at a 
> loss, and would love to ride my beloved Leo without worrying about whether 
> my front derailleur will blow up again.
>
> Cat
>
> [image: IMG_1018.jpg][image: 715737051.jpg]
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/ab19e8d4-917e-4927-8d8d-a58c60801c5bn%40googlegroups.com.

[RBW] Re: Sacramento Ride recommendations

[Wesley]

If you can drive to your ride, then I'd suggest parking at the Yolo Bypass 
Wildlife Area and riding the gravel roads through there. It's beautiful, 
full of wildflowers and migrating birds, and completely flat. If you'd 
prefer terrain, there are a lot of options in the Sierra foothills. One 
good one is to drive to the Quarry Trail and ride it (north of Folsom Lake 
near the confluence of the North and Middle forks of the American River - 
that confluence area is the starting points for a lot of good hiking and 
riding, though bikes generally aren't allowed on the single-track trails.
-Wes

On Friday, September 1, 2023 at 2:04:52 PM UTC-7 Wesley wrote:

> The American River Bike Trail is exceptional. If by Northeast Sac you mean 
> one of the suburbs like Citrus Heights or Roseville, then I'd suggest 
> riding Auburn-Folsom Road. There's a lot of mixed terrain to ride on the 
> levees (which al have a gravel road on top and/or to the side) but they get 
> boring very fast (for me). If you can drive to the start of your ride then 
> your options are much greater.
> -Wes
>
> On Friday, September 1, 2023 at 12:41:38 PM UTC-7 Brendan Willard in SF 
> wrote:
>
>> I'll be out in North East Sac this weekend and hope to get a 20-40 mile 
>> ride or two in.  Any musts? Mixed terrain preferred.
>>
>> Thanks,
>> Brendan in SF.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/b0af1c3c-c303-4186-a8e4-44bc57ea3d5cn%40googlegroups.com.

[RBW] Re: Sacramento Ride recommendations

[Wesley]

The American River Bike Trail is exceptional. If by Northeast Sac you mean 
one of the suburbs like Citrus Heights or Roseville, then I'd suggest 
riding Auburn-Folsom Road. There's a lot of mixed terrain to ride on the 
levees (which al have a gravel road on top and/or to the side) but they get 
boring very fast (for me). If you can drive to the start of your ride then 
your options are much greater.
-Wes

On Friday, September 1, 2023 at 12:41:38 PM UTC-7 Brendan Willard in SF 
wrote:

> I'll be out in North East Sac this weekend and hope to get a 20-40 mile 
> ride or two in.  Any musts? Mixed terrain preferred.
>
> Thanks,
> Brendan in SF.
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/50d49bb7-44b2-48b5-b58a-e3cd67137638n%40googlegroups.com.

[ovirt-users] Re: How to use Python to manage each node in batches, because I want to send some scripts to nodes in batches

[Wesley Stewart]

Not sure what you did.  But this seems more like normal server management.
Not sure what you are trying to do, but it seems like ansible might fit the
bill here.

On Thu, Aug 17, 2023, 11:14 PM ziyi Liu  wrote:

> I have found a solution to log in to each host without password
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/TU3SDAR2RBDYSFHZQFKVWQH3EFWNEVKE/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YMZLJ5H5PLDD7GXXBZMIMHILZMVZKLIV/

Re: [RBW] A College Clem

[Wesley]

The current best value from Surly is the Cross Check, at $1100 for a 
complete.
-W

On Friday, August 11, 2023 at 1:00:16 PM UTC-7 Eric Daume wrote:

> The 1x1 isn’t made any more, and they hold their value really well as they 
> seem to be coming somewhat collectible. The replacement is the Lowside, I 
> think it’s about $890 for the frame set. Not really a value play anymore. 
>
> Eric
>
>
> On Friday, August 11, 2023, George Schick  wrote:
>
>> I'll chime in with yet another recommendation (would be my choice if I 
>> were going to be shipping a kid of to a campus in the near future):  a 
>> Surly 1x1. They're single speed frames, rather on the heavy side made from 
>> 4130 chro-moly tubing, powder coated for durability, and can be set up with 
>> a single-speed cog and chainring of your choice.  I currently own one and 
>> use it as my all around utility bike for running short haul errands, etc.  
>> I'm using a Bulletproof BMX crankset, 38-tooth Rocket chainring, and a 
>> Shimano 17-tooth SS freewheel for a 59" gear (perfect for riding around 
>> campus).  You can equip this bike with front and rear disc brakes, though I 
>> would not recommend it for campus use where it can get beat around on an 
>> overloaded bike rack and the discs bent. Instead I'd set it up with 
>> linear-pull F brakes. It comes with a threadless fork/steering tube, 
>> though, so you'd need the right length/angle threadless stem and the right 
>> bars to fit it (I'd recommend the VeloOrange Granola-Moose bar for easy 
>> mounting of the bar with a headlight.  You could pick any hub, rim, and 
>> tire combination you prefer.  Mine has Surly's semi-sealed cartridge hubs 
>> with 28mm rims and 60mm Schwalbe Big Apple balloon tires - again, a perfect 
>> combo for campus riding.
>> A web search shows that there are several LBS's around the GR, MI area 
>> who are Surly dealers so you'd be within reasonable reach of one.  Anyway, 
>> that's my 2¢.
>>
>> PS: I have a 16T White Industries SS freewheel FS if that would work
>>
>> On Wednesday, August 9, 2023 at 6:47:48 AM UTC-5 Bicycle Belle Ding Ding! 
>> wrote:
>>
>>> Wow, this thread has generated a lot of response, and I’ve enjoyed 
>>> reading every post. It’s such a shame we have to go to extremes to avoid 
>>> bike theft - carrying heavy u-locks, being so choosy about parking and 
>>> locking, replacing parts, making the bike ugly, choosing to ride an 
>>> undesirable bike so we can preserve our desirable bike…
>>>
>>> Then there’s the other variable - how careful is the kid going to be 
>>> with the bike? Well, bikes are not precious to him. He likes his bike, sees 
>>> beauty and usefulness in it, but please do not bore him with too many 
>>> details about it. I don’t think he will worry about it like I would; and 
>>> that may lead to carelessness that gets his bike stolen. But also, he has 
>>> the Mr. Magoo-like quality of walking through life blissfully unaware of 
>>> the evil that lurks around every corner and arriving unscathed at his 
>>> destination. 
>>>
>>> The campus in question does not have a lot of bike pirates roaming 
>>> about, although yes, I know they exist everywhere. But they are not 
>>> prolific on this particular campus. I’m still undecided about what bike to 
>>> send, but any bike that goes with him will get skewers that are locked and 
>>> nuts that prevent the theft of stem, saddle and seat post. Hexlox makes all 
>>> these products, if anyone is wondering. We’ll have good u-locks, too. 
>>>
>>> And thanks to Jim for the mention of coverage under homeowners’ 
>>> insurance. I’ll be looking into that for sure. 
>>> Leah
>>>
>>> On Tuesday, August 8, 2023 at 7:04:07 PM UTC-4 nlerner wrote:
>>>
 Similar to Mackenzy, I’ve been bike commuting to college campuses for 
 many decades, the last 30 of which have been in the Boston area. I’ve 
 never 
 had a bike stolen likely because (1) I use a decent lock and (2) never 
 park 
 it outside overnight. I have colleagues who would never leave their bikes 
 outside at all and schlep them up to their offices, navigating too small 
 elevators and lots of doorways, but I’ve never seen the need. Sure, bikes 
 get stolen around here all the time, but I’m convinced those are the ones 
 easiest to steal, e.g., unlocked on a porch or in a backyard or part of a 
 larger home break in.

 Now that doesn’t mean I necessarily endorse bringing the Clem to 
 college as it will likely get thoroughly trashed from daily wear and tear 
 (bike racks are not bike-friendly spaces). But I’m also always looking for 
 an excuse to build up a commuter for colleagues.

 Neal Lerner
 Brookline MA

 On Tuesday, August 8, 2023 at 5:07:52 PM UTC-4 Mackenzy Albright wrote:

> I'm amazed at the amount of discouragement of use of the Clem as a 
> college commuting bike. 
>
> I've worked at universities a good chunk of my life and commuted 

Re: [RBW] Re: A College Clem

[Wesley]

Hi Kim,
The way to measure is from one axle to the other. The maximum measurement 
that will fit on bike racks on Sacramento busses (pretty much identical to 
racks I've used/seen in other cities) is approximately 45".
-Wes
On Wednesday, August 9, 2023 at 9:14:41 AM UTC-7 krhe...@gmail.com wrote:

> @ Jonathan -
>
> Does the Clem H and the Clem L have the same wheelbase or not ?
>
> I know my Clem L from the outer length from end to end of the wheels 
> measures close to 80" long. Too long for a bike rack for a transit bus is 
> my belief.
>
> Kim Hetzel
> Yelm, WA. 
>
> On Wednesday, August 9, 2023 at 7:36:47 AM UTC-7 Johnny Alien wrote:
>
>> I mean the fallback is to take the smaller Clem H. It will be easier to 
>> get onto public transport bike racks and be easier to slot into a dorm at 
>> night too. The choice doesn't have to be Clem L or total beater. That Clem 
>> H is a killer bike that has slightly less sentimental value if it happens 
>> to get stolen. If it doesn't then he knows he can go with the bigger one 
>> the next semester. 
>>
>> On Wednesday, August 9, 2023 at 9:58:42 AM UTC-4 Curtis wrote:
>>
>>> If this is a question of bicycle happiness level (BHL)for a first year 
>>> college student we may be spending more energy on this than we should.  
>>> Difficult to judge the BHL for an 18 y.o. when we are looking at this 
>>> through our rose or not so rose colored glasses.  Who is to say the student 
>>> on the 100 dollar "beater" has a different BHL compared to the student on 
>>> the 2500 dollar bicycle?  
>>>
>>> Perhaps only the rider knows.
>>>
>>> Perhaps we should hope that the student is indifferent about the bicycle 
>>> they ride and are focused on the task at hand.  
>>>
>>> If this bicycle and not that bicycle makes the student happier at 
>>> college then pick this bicycle.
>>>
>>> Peace,
>>> Curtis
>>>
>>> On Wed, Aug 9, 2023, 4:47 AM Bicycle Belle Ding Ding! <
>>> jonasa...@gmail.com> wrote:
>>>
 Wow, this thread has generated a lot of response, and I’ve enjoyed 
 reading every post. It’s such a shame we have to go to extremes to avoid 
 bike theft - carrying heavy u-locks, being so choosy about parking and 
 locking, replacing parts, making the bike ugly, choosing to ride an 
 undesirable bike so we can preserve our desirable bike…

 Then there’s the other variable - how careful is the kid going to be 
 with the bike? Well, bikes are not precious to him. He likes his bike, 
 sees 
 beauty and usefulness in it, but please do not bore him with too many 
 details about it. I don’t think he will worry about it like I would; and 
 that may lead to carelessness that gets his bike stolen. But also, he has 
 the Mr. Magoo-like quality of walking through life blissfully unaware of 
 the evil that lurks around every corner and arriving unscathed at his 
 destination. 

 The campus in question does not have a lot of bike pirates roaming 
 about, although yes, I know they exist everywhere. But they are not 
 prolific on this particular campus. I’m still undecided about what bike to 
 send, but any bike that goes with him will get skewers that are locked and 
 nuts that prevent the theft of stem, saddle and seat post. Hexlox makes 
 all 
 these products, if anyone is wondering. We’ll have good u-locks, too. 

 And thanks to Jim for the mention of coverage under homeowners’ 
 insurance. I’ll be looking into that for sure. 
 Leah

 On Tuesday, August 8, 2023 at 7:04:07 PM UTC-4 nlerner wrote:

> Similar to Mackenzy, I’ve been bike commuting to college campuses for 
> many decades, the last 30 of which have been in the Boston area. I’ve 
> never 
> had a bike stolen likely because (1) I use a decent lock and (2) never 
> park 
> it outside overnight. I have colleagues who would never leave their bikes 
> outside at all and schlep them up to their offices, navigating too small 
> elevators and lots of doorways, but I’ve never seen the need. Sure, bikes 
> get stolen around here all the time, but I’m convinced those are the ones 
> easiest to steal, e.g., unlocked on a porch or in a backyard or part of a 
> larger home break in.
>
> Now that doesn’t mean I necessarily endorse bringing the Clem to 
> college as it will likely get thoroughly trashed from daily wear and tear 
> (bike racks are not bike-friendly spaces). But I’m also always looking 
> for 
> an excuse to build up a commuter for colleagues.
>
> Neal Lerner
> Brookline MA
>
> On Tuesday, August 8, 2023 at 5:07:52 PM UTC-4 Mackenzy Albright wrote:
>
>> I'm amazed at the amount of discouragement of use of the Clem as a 
>> college commuting bike. 
>>
>> I've worked at universities a good chunk of my life and commuted with 
>> high(er) end bikes and never had any issues. I like riding nice bikes - 
>> 

[RBW] Re: FS: Cliffhanger Tandem/Cargo Wheelset

[Wesley]

Tandem rear wheels typically have 145mm spacing, wider than the typical 
135mm spacing of non-tandem rear wheels, and closer to modern "fat bikes". 
Some adaptation may be possible, I don't know.
-Wes

On Sunday, August 6, 2023 at 3:21:26 PM UTC-7 Bones wrote:

> Yes. A 56 Susie takes a 29" tire. Somebody please correct me if I am wrong.
>
> Bones
>
> On Sunday, August 6, 2023 at 3:25:56 PM UTC-4 Justin Kennedy wrote:
>
>> Sorry maybe a dumb question but would these work with QR on a 56cm Susie?
>>
>> On Saturday, August 5, 2023 at 7:38:38 PM UTC-4 Bones wrote:
>>
>>> Knew I'd miss something. 29ers!
>>>
>>> Thanks, 
>>> Bones
>>>
>>> On Saturday, August 5, 2023 at 7:19:15 PM UTC-4 Wesley wrote:
>>>
>>>> Hi Bones, 
>>>> What wheel size, please?
>>>> -Wes
>>>>
>>>> On Saturday, August 5, 2023 at 12:08:51 PM UTC-7 Bones wrote:
>>>>
>>>>> I bought these from Velocity a few years ago. I replaced the front hub 
>>>>> with a Shimano dynamo. 40H rear, 36H front. Both rims have machined 
>>>>> sidewalls. The rear has a bolt-on rotor mount, the front is centerlock 
>>>>> (dust cover included).They are black but they have a subtle color to 
>>>>> them, 
>>>>> can't quite explain it. I think they look cool. Hopefully the pictures 
>>>>> show 
>>>>> it. They haven't seen all that much use. Skewers included. $400 shipped 
>>>>> (or 
>>>>> best offer) lower 48.
>>>>>
>>>>> [image: wheels01.jpg][image: wheels02.jpg][image: wheels03.jpg][image: 
>>>>> wheels04.jpg]
>>>>> Thanks,
>>>>> Bones
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/616e9b1d-19b5-4c15-860b-31fc8cb29adcn%40googlegroups.com.

[RBW] Re: FS: Cliffhanger Tandem/Cargo Wheelset

[Wesley]

Hi Bones, 
What wheel size, please?
-Wes

On Saturday, August 5, 2023 at 12:08:51 PM UTC-7 Bones wrote:

> I bought these from Velocity a few years ago. I replaced the front hub 
> with a Shimano dynamo. 40H rear, 36H front. Both rims have machined 
> sidewalls. The rear has a bolt-on rotor mount, the front is centerlock 
> (dust cover included).They are black but they have a subtle color to them, 
> can't quite explain it. I think they look cool. Hopefully the pictures show 
> it. They haven't seen all that much use. Skewers included. $400 shipped (or 
> best offer) lower 48.
>
> [image: wheels01.jpg][image: wheels02.jpg][image: wheels03.jpg][image: 
> wheels04.jpg]
> Thanks,
> Bones
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/0d07986b-5957-4975-ab86-c6bf4f60n%40googlegroups.com.

Re: [RBW] Re: Club Rides On A Racing Platypus

[Wesley]

OMG this is so cute!
-W

On Thursday, August 3, 2023 at 6:12:31 PM UTC-7 Bicycle Belle Ding Ding! 
wrote:

> I really do have the sweetest, cutest story from the Tuesday night women’s 
> ride. 
>
> We had a small group of 7 riders that night. We were several miles in when 
> suddenly from behind, I heard two unfamiliar voices, one belonging to a 
> child, and one belonging to a man. I looked back and was astounded - there 
> at the end of our peloton was an 8 year old girl on a tiny blue Trek bike, 
> wearing her matching blue helmet, blonde hair flying and huge grin on full 
> display. I looked at her father, helmetless and riding his own bike. He 
> wore a look half proud and half sheepish. “This is Braelyn, and she’s been 
> watching you go by every week,” he said. “And she’s been wanting to ride 
> with you; she said, ‘Daddy, Tuesday night at 6:50 they’ll be here.’ And she 
> got ready so she could join you tonight.” I looked at my speedometer…we 
> were riding at over 17 mph. She moved up behind me and another woman fell 
> in behind her. 
>
> “Ok, honey, you listen for when I call out things like stick or hole, ok?” 
>
> “Ok!” she said, flashing a Cheshire Cat grin. And we pedaled on, flying 
> over country roads with our tiny companion and her daddy. She stayed with 
> us for a few miles and then they peeled off after the second set of 
> railroad tracks. I wish I had gotten a photo, but maybe next week we’ll see 
> her again and I’ll get my chance.
>
> I’m sure we were in violation of like 30 club rules but Michigan doesn’t 
> scold you for things like these. Braelyn and her little Trek, legs flying 
> and hair streaming…I doubt we will ever see anything better than her on the 
> Tuesday Night Ride.
> On Wednesday, September 14, 2022 at 4:38:01 PM UTC-4 Patrick Moore wrote:
>
>> Delicious!
>>
>> On Fri, Sep 9, 2022 at 3:58 PM Bicycle Belle Ding Ding! <
>> jonasa...@gmail.com> wrote:
>>
>>> ... Some guy will come find me at my vehicle and tell me how I’m doing 
>>> it wrong. After getting lectured about how I could go 25% faster if I had 
>>> this bike and narrow tires, blah, blah, I say, “Well, I just beat you, so I 
>>> don’t think my bike is the problem.”  
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/5f065da3-4c76-40b9-bffe-db9a0b538944n%40googlegroups.com.

[RBW] Re: new member/delta quill stem risers

[Wesley]

I probably should not blow up my own spot like this (I use two of these on 
my bikes and may soon need a third, I love them). But this from Soma 
Fabrications is 1) brand new, 2) the same price, and 3) a much higher rise.

https://www.somafabshop.com/shop/soma-high-rider-xl-quill-28-6-22-2-290mm-4984#attr=2406

These are the only risers that can make a typical "large" (usually about 
60cm) bike from yesteryear comfortable for me. I love them, but keep in 
mind that they are machined rather than forged and heat treated like a 
Nitto product, so probably don't use one on a mountain bike that will see 
rough trail use.
-Wes

On Friday, August 4, 2023 at 8:11:10 AM UTC-7 chasenl...@gmail.com wrote:

> hi all! i have posted a couple times but never really introduced myself. I 
> am Chasen, I live in NYC, and I've got a roadini and a gus, both orange, 
> with an atlantis in the mail from c & l. i also have a 650b'd rb 2 that i 
> cant place a year on,  a 1990 stumpjumper w a Clydesdale fork, and a junker 
> old huffy mtb thing that i conduct stupid experiments on. 
>
> These convos are such a great resource for young and dumb wannabe bike 
> mechanics like myself, and you all seem much less grumpy than the folks 
> over on reddit. For these things, I thank you all.
>
> *alright, heres the important part of this post:*
>
> What have the groups experiences been with delta quill stem risers of 
> yore? 
>
> https://www.ebay.com/itm/305021101084
>
> I became aware of them through this article on the riv site:
> https://www.rivbike.com/pages/nitto-stem-comparison
> I found one cheap on ebay and its on the way to me now. Just wondering 
> what everyone thinks of these! I am pretty excited to try it just for the 
> novelty of it, though im sure theres a reason they're not readily available 
> anymore. If anyone has pics of one in use, please share!
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/689985fd-f742-40d1-a499-76657960b931n%40googlegroups.com.

[RBW] Re: Swapping a bulb in a Schmidt Edelux II?

[Wesley]

I would suspect the wiring and connections well before thinking the LED had 
burned out. Maybe clean and re-connect the wires everywhere you can? If 
there is a soldered connection in the wire, it may need re-doing? Good luck!
-Wes

On Thursday, August 3, 2023 at 9:07:36 AM UTC-7 Caroline Golum wrote:

> Dynamo-freaks: anyone ever replace a bulb in their Edelux II light? Mine 
> was flickering for a while, then went totally out on my ride home last 
> night. Checked the connection and it's plugged into the hub - but, worth 
> noting, the hub is a recent replacement!

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/58b4da12-4c46-4a5a-8bb3-86cbd8b9eec6n%40googlegroups.com.

[RBW] Re: Tried and liked: Suntour Cyclone pretzel

[Wesley]

Last fall I wrecked a derailer and bent the hanger when I shifted a 
short-cage rear der into the big-big combination. I bought a new derailer 
and aligned the dropout using this 
clever hack (which I could swear I learned of from this 
list): https://youtu.be/TnwreRrorIA

Anyway, it sounds to me like after all these tries that your derailer 
hanger is aligned, and that the problem lies elsewhere. Perhaps a bent cog 
on the cassette? Or the new derailer you're trying has some flaw - e.g. the 
upper pulley can wander? A stiff link in the chain? I can't think of a 
reason that the impact to shifter, cable, and housing would be the issue, 
but maybe there is one I haven't thought of?

"When you have eliminated the impossible, whatever remains – however 
implausible – must be the truth."
-Wes
On Thursday, August 3, 2023 at 6:00:36 AM UTC-7 Bill Schairer wrote:

> I vote for buy a gauge and do it yourself.  I bought a Park DAG years ago 
> after a wreck and have used it many, many times since.  No regrets.  
> Haven't I watched your build videos?  You need this tool regardless.  That 
> said, if a shop used one and aligned the hanger, I have a lot of trouble 
> thinking the hanger is responsible for the jumping. In my experience, a 
> misaligned hanger results in poor shifting, noisy drivetrain, and 
> difficulty adjusting the high and low stops.  If it is jumping between 
> gears, maybe, but then should be happening in all gears or at least never 
> seem quite right no matter which gear?  If it is jumping on the same gear, 
> I'd be thinking chain, cassette and/or chainrings?
>
> Bill S
> San Diego
>
> On Wednesday, August 2, 2023 at 8:20:22 PM UTC-7 eric...@gmail.com wrote:
>
>> Okay, some mild updates. 
>>
>> I've bent and tweaked the hanger with crescent wrenches at least two 
>> dozen times now. Worked on it during the miserable heat wave here and 
>> during nicer weather yesterday. During the process I remove the chain and 
>> the derailer, tweak the hanger, re-install the chain and derailer, test 
>> ride. Repeat. Over and over! Every time I ride the bike the chain skips. 
>>
>> I've tried aligning by hand and eye. I've used a series of straight 
>> edges, trying to reference off the cassette to the face of the derailer 
>> hanger where the derailer sits. I can get the straight edges into plane 
>> with one another but evidently that's not enough because the chain still 
>> jumps. 
>>
>> I feel like I can finesse this thing back into working order but I have 
>> so far been unsuccessful. The hanger is relatively flat considering how 
>> mangled it got. It's considerably better than it was. The bolt hole is 
>> elongated but fortunately derailer bolts screw in nicely and the threads 
>> feel good. Through all my uninstalling/reinstalling the bolts thread in 
>> nicely each time. 
>>
>> One problem is that the guys at the LBS have put their dropout and hanger 
>> alignment tools on the bike and they say the tools show things are aligned. 
>> *But* they are also audibly and visibly weary of putting too much torque 
>> on the hanger and seem to think it's going to shear off the frame if they 
>> look at it funny. I don't think that's going to happen. I talked to Grant 
>> about this twice now and he doesn't think that's going to happen, either. 
>> He shared an acedote wherein he bent a derailer hanger through 180º of 
>> motion several times before the hanger sheared off. I'm not moving mine 
>> nearly as much, just a bit at a time. And today I heard Grant Petersen say 
>> "Steel is magical." So I'm adding that to my lifetime book of memorable 
>> quotes by notable people. 
>>
>> There's another shop in town but I get bad vibes every time I go in there 
>> so I'm going to spare myself and stay away. I know if I go in there it'll 
>> end up being a bad scene and I'll regret it. 
>>
>> I'm open to having a builder try to align the hanger, heat it up and 
>> shape it or braze a new dropout onto the frame. But the builder I know and 
>> have worked with before on three other bikes (this Hillborne included) has 
>> sold his tools and retired. Two other nearby builders haven't returned my 
>> messages. 
>>
>> Now I'm thinking the best next step is to drop > $100 on a derailer 
>> hanger alignment tool and try it myself in the home shop. Looking at the 
>> Park Tool DAG 2.2. This eliminates the hesitancy of other mechanics (I'm 
>> not afraid to wreck the bike) and gives me a useful tool to have forever. 
>>
>> Full options going forward (as I see them, open to suggestions as 
>> always): 
>>
>>- Buy a gauge and adjust it myself until I'm satisfied or I give up 
>>and advance to next option
>>- Take it to a shop
>>   - Go-to shop seems afraid to break my hanger, I don't think that's 
>>   going to happen but they are audibly and visibly weary. 
>>   - Other shop in town I avoid at all costs and don't want to take 
>>   my bikes to them
>>- Get a new dropout welded onto the bike
>>  

Re: [RBW] Re: Clem Smith, Jr for sa;e

[Wesley]

Mike, will you pease tell us your location and the price of the bike?

Kim, it is a 64cm in the photo (you can tell by how tall the headtube is)
-Wes

On Wednesday, August 2, 2023 at 8:44:55 AM UTC-7 krhe...@gmail.com wrote:

> The frame size is 52cm, not a 64cm frame.
>
> Kim Hetzel.
>
> On Wed, Aug 2, 2023, 8:38 AM Hoch in ut  wrote:
>
>> I’m assuming this is a 64cm frame. 
>>
>> Best wishes to the sale and more importantly, your health. 
>>
>> On Tuesday, August 1, 2023 at 4:44:31 PM UTC-6 eclec...@gmail.com wrote:
>>
>>> Hi,
>>> I had a Clem Smith, Jr built at RBW in Walnut Creek about 1 1/2 years 
>>> ago. Shortly after the purchase I had surgery on my upper left leg that 
>>> doesn’t allow to sit in the bicycle saddle without pain. So reluctantly 
>>> I’ve decided to sell it.
>>>
>>> Clem Smith, Jr mens 54 cam
>>> Ergon handlebar grips
>>> Ergon SL Core Prime Mens
>>> Lumina Micro 650 front light
>>> Handlebar mounted clock
>>> Water holder
>>> Silver fender 
>>> Abus folding lock and mounted holder
>>> Busch and Muller handlebar mounted mirror
>>> Look trail pedals
>>> Nitto rear rack
>>> Rear light
>>> Mike Lipelt
>>> eclec...@gmail.com
>>> Rear light
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "RBW Owners Bunch" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/rbw-owners-bunch/eS8Z-BMUvsQ/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> rbw-owners-bun...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/rbw-owners-bunch/96b163c1-6ca0-41eb-8439-e340045b052an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/d4712264-0d16-42f8-b644-6d4c15cbe9dfn%40googlegroups.com.

Re: [RBW] Tried and liked: Suntour Cyclone pretzel

[Wesley]

Possibly dumb question: have you taken a good look at your chain? It ay be 
kinked, which would cause skipping gears.
-Wes

On Wednesday, July 26, 2023 at 4:04:01 PM UTC-7 eric...@gmail.com wrote:

> Andre attempted to make some further adjustments, the chain still skips. I 
> tried installing a Deore XT M771 and that was a little bit better but the 
> chain still skips. 
>
> I called Riv and talked to Grant who was eager to see some pictures. Will 
> has a new dropout heading to me by mail, now I just need to find someone 
> who can braze the new dropout on. The framebuilder I know has transitioned 
> from building bikes to chartering boats! 
>
> On Tuesday, July 25, 2023 at 8:43:30 PM UTC-4 Eric Marth wrote:
>
>> Yesterday I brought the frame to my LBS, Bike Works and handed it over 
>> to trusted mechanic Andre. He bent the hanger, aligned the dropouts and 
>> aligned the hanger. The hanger alignment tool showed the hanger was in 
>> plane with the rim. Amazingly the hole took a derailer bolt just fine. It 
>> looks terrible but functionality seemed promising. This was all I cared 
>> about.
>>
>> You can see the hole is terribly elongated. 
>>
>> [image: IMG_6872.JPG] 
>>
>> [image: IMG_6871.JPG]
>>
>> Here's my wavy hanger.
>>
>> [image: IMG_6880.JPG]
>>
>> Fortunately I have a small collection of Cyclones to draw from. The last 
>> one I mangled was beautiful old stock. This one here is almost as nice. 
>>
>> The bike shifted fine in the stand. But on the road and under load the 
>> chain skips in the smallest four cogs. 
>>
>> Tomorrow I'll take it back to Andre and see if he can't finesse it into 
>> shape. 
>> On Tuesday, July 25, 2023 at 8:38:04 PM UTC-4 Eric Marth wrote:
>>
>>> Patrick: Sorry about that Fargo but glad to hear it could be repaired. 
>>> Replaceable hangers seem helpful!
>>>
>>> On Monday, July 24, 2023 at 10:41:41 AM UTC-4 Patrick Moore wrote:
>>>
 And: I had Chauncey Matthews use a replaceable hanger when he built the 
 replacement for the Fargo.

 On Mon, Jul 24, 2023 at 8:38 AM Patrick Moore  
 wrote:

> FWIW, I had a similar experience with a Fargo when a stick jammed the 
> rd: the hangar was bent 90* inward (and jammed into the cassette; no 
> single-speeding home). The good news, and the point: a LBS was able to 
> unbend the rd to usable status again. The replacement rd worked fine. Of 
> course, YMMV.
>
>
>
> On Mon, Jul 24, 2023 at 7:50 AM Eric Marth  wrote:
>
>> Many thanks, John. I'll check out the spokes. 
>>
>> I've been texting with my local mechanic friend, Andre. We're going 
>> to try and bend the hanger and see how close we can get it. Considering 
>> a 
>> drop out saver from Wheels Mfg. 
>>
>> If that fails I'll see about having a new dropout installed. I gotta 
>> call Will when Riv opens!
>>
>> On Monday, July 24, 2023 at 8:36:56 AM UTC-4 JohnS wrote:
>>
>>> Wow Eric, that was a bad one, glad your ok and the Sam is on the 
>>> mend. Don't forget to check the spokes for nicks, could break easy if 
>>> they 
>>> are.
>>>
>>> JohnS
>>>
>>>
>>> On Monday, July 24, 2023 at 7:54:06 AM UTC-4 Josh C wrote:
>>>
 Wow. That's wild. Glad you're ok. Bummer about the Sam, that's a 
 beautiful bike.

 On Sunday, July 23, 2023 at 9:08:55 PM UTC-4 eric...@gmail.com 
 wrote:

> Thanks Brian and Danny! 
>
> I got the mech freed. The parallelogram housing is twisted, too. 
> The limit screws aren't in plane, they're twisted! It's a huge mess. 
> Still 
> have many good screws, bolts and springs worth saving. Jockey wheels, 
> too. 
> I'll leave it as-is and pull parts from it as needed. 
>
> On Sunday, July 23, 2023 at 8:19:03 PM UTC-4 Danny wrote:
>
>> Sorry about the hanger damage, but good to hear that you're ok. 
>> Even in its pretzelized state, it's a good looking derailer 
>> sculpture!
>>
>> -Danny
>>
>>
>> On Sun, Jul 23, 2023 at 6:42 PM Brian Turner  
>> wrote:
>>
>>> I’m just over here hungry for pretzels.
>>>
>>> Seriously though, glad you’re ok, and I’m sorry about your Sam’s 
>>> hanger. I’m sure it’ll be up and running strong again soon.
>>>
>>> On Jul 23, 2023, at 6:57 PM, Eric Marth  
>>> wrote:
>>>
>>> Thanks, Jim. Just a bit of my own patented brand of sarcasm ;) 
>>>
>>> The damage is waaay out of proportion to the fall. 
>>>
>>> On Sunday, July 23, 2023 at 5:57:30 PM UTC-4 J J wrote:
>>>
 Wow... the most important thing is that you're fine, Eric. The 
 bike stuff is "just" bike stuff, repairable or replaceable.

 I saw your subject line 

[RBW] Re: Forks and adjusting headsets

[Wesley]

Oh, and to be more practical: If you can turn the top (lock) nut by hand, 
it is not doing anything. I am not sure why the video recommends backing 
off the lock nut, but I don't think you should. The "lock" function comes 
from tightening that nut until it stretches the steerer. Taken to the 
extreme, this will cause the threaded section to be in tension between the 
lower and upper nuts until turning either nut in either direction would 
feel like "tightening" it. Hence, the nuts are locked. This is how the lock 
nuts on loose-bearing hubs work, for instance. You don't need to go to that 
extreme on the headset, since the upper bearing doesn't really do anything 
other than keep the steerer centered (the bottom bearing carries all the 
weight). So just go ahead and turn the lock nut until it is snug 
(guesstimating: 15 ft-lbs) and go ride.
-W
On Tuesday, July 25, 2023 at 10:00:56 AM UTC-7 Wesley wrote:

> This advice all applies only to threaded forks (all Rivs except Gus and 
> tandem):
> 1. Use as many spacers as necessary so that the lock nut (top nut) is 
> fully engaged with the threads but doesn't bottom out.
> 2. Most (or all) threaded forks have a key groove in the steer tube, 
> cutting vertically through the threads (it is barely visible at 4:23 in the 
> video you linked). A lock washer goes on the stack above the bottom nut 
> (which is the top bearing's inner race), with a tab or "key" that fits in 
> this groove. As a result, the lock washer cannot spin relative to the steer 
> tube. Thus, friction from the spinning of the locknut and spacers above 
> this lock washer cannot cause the bottom nut to spin. So that bottom nut 
> will stay where you left it, even though you may crank down the top (aka 
> lock) nut with just one wrench.
> 3. There is an ideal tightness to which you will set the bearing. But the 
> lock nut works by stretching the steel of the steer tube (just a tiny bit!) 
> until the threads don't engage the bottom nut (this is why the bottom nut 
> doesn't work loose over rough terrain). Stretching the steer tube elongates 
> it, so the bearings get looser. Therefore, you must adjust the bearing to 
> be too tight before the locknut goes on, so that the stretching brings the 
> bearing to ideal tightness. Accomplishing this requires a feel that 
> develops over time. Or you could just get a sealed-bearing headset, which 
> allow much more leeway in bearing adjustment without feeling loose or tight 
> (because a sealed bearing headset squeezes the bearing races, not the 
> balls.)
>
> Hope this helps!
> -Wes
> On Tuesday, July 25, 2023 at 8:33:48 AM UTC-7 maxcr wrote:
>
>> There was a conversation on the Roadini thread 
>> <https://groups.google.com/u/5/g/rbw-owners-bunch/c/tAas6urcOwg> about 
>> adjusting the headset after fork removal.  This is something I've wondered 
>> for a while - some say you need to wrenches others one, my experience is if 
>> I tighten and back a bit I can move the nut with my hand.
>>
>> Does anyone have a solid explanation of how it's done? When installing 
>> one of my forks on a new bike I had found this video  
>> <https://vimeo.com/143667109>from Rivendell where you can see the 
>> process but I'm still unsure of how tight I should go? Should I use a 
>> wrench or is it enough to hand tighten?
>>
>> Also, how many spacers should one use when setting up a fork?
>>
>> Thanks
>> Max
>>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/54016ee8-3f72-4c2c-b53f-9b85a876df40n%40googlegroups.com.

[RBW] Re: Forks and adjusting headsets

[Wesley]

This advice all applies only to threaded forks (all Rivs except Gus and 
tandem):
1. Use as many spacers as necessary so that the lock nut (top nut) is fully 
engaged with the threads but doesn't bottom out.
2. Most (or all) threaded forks have a key groove in the steer tube, 
cutting vertically through the threads (it is barely visible at 4:23 in the 
video you linked). A lock washer goes on the stack above the bottom nut 
(which is the top bearing's inner race), with a tab or "key" that fits in 
this groove. As a result, the lock washer cannot spin relative to the steer 
tube. Thus, friction from the spinning of the locknut and spacers above 
this lock washer cannot cause the bottom nut to spin. So that bottom nut 
will stay where you left it, even though you may crank down the top (aka 
lock) nut with just one wrench.
3. There is an ideal tightness to which you will set the bearing. But the 
lock nut works by stretching the steel of the steer tube (just a tiny bit!) 
until the threads don't engage the bottom nut (this is why the bottom nut 
doesn't work loose over rough terrain). Stretching the steer tube elongates 
it, so the bearings get looser. Therefore, you must adjust the bearing to 
be too tight before the locknut goes on, so that the stretching brings the 
bearing to ideal tightness. Accomplishing this requires a feel that 
develops over time. Or you could just get a sealed-bearing headset, which 
allow much more leeway in bearing adjustment without feeling loose or tight 
(because a sealed bearing headset squeezes the bearing races, not the 
balls.)

Hope this helps!
-Wes
On Tuesday, July 25, 2023 at 8:33:48 AM UTC-7 maxcr wrote:

> There was a conversation on the Roadini thread 
>  about 
> adjusting the headset after fork removal.  This is something I've wondered 
> for a while - some say you need to wrenches others one, my experience is if 
> I tighten and back a bit I can move the nut with my hand.
>
> Does anyone have a solid explanation of how it's done? When installing one 
> of my forks on a new bike I had found this video  
> from Rivendell where you can see the process 
> but I'm still unsure of how tight I should go? Should I use a wrench or is 
> it enough to hand tighten?
>
> Also, how many spacers should one use when setting up a fork?
>
> Thanks
> Max
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/67d5fd0d-0add-487d-8231-266b5f7b0daen%40googlegroups.com.

Re: [RBW] Re: ISO Roadini...or?

[Wesley]

The two wrenches are to hold one nut still while turning the other, like 
when serving loose bearing hubs. Most (all?) threaded headsets use a keyed 
washer between the nuts to prevent one from turning the other, so there's 
no need for two wrenches. If you want to travel with a bike with threaded 
headset, it is worth using a sealed-bearing headset. For one, you can't 
lose some of the balls, and for another the preload adjustment is much less 
sensitive.

On Monday, July 24, 2023 at 10:04:35 AM UTC-7 pi...@gmail.com wrote:

> Haha. I haven't touched my Chris King threadless headset on my touring 
> bike for years. Getting all the play out took quite a bit of futzing so now 
> I avoid messing with it.   For a threaded headset I remember you need 2 
> wrenches. Just one more thing I don't want to deal with while I'm 
> jet-lagged and putting together the bike at a hotel under time pressure.
>
> On Monday, July 24, 2023 at 9:55:40 AM UTC-7 chasenl...@gmail.com wrote:
>
>> Piaw- it does, I was intimidated but I saw a plp vid where he uses the 
>> case w a threaded fork, so I just got one of those mini adjustable wrenches 
>> that Riv sells and it’s p smooth sailing as long as you keep up with 
>> everything. I saw Russ posting recently about some Topeak travel-specific, 
>> light-looking, flat headset wrenches that would be amazing for this 
>> application, but they most be a prototype, can’t find them anywhere.
>>
>> On Mon, Jul 24, 2023 at 12:35 PM Piaw Na(藍俊彪)  wrote:
>>
>>> Doesn't the post-transfer case require fork removal? Is that hard to do 
>>> on the threaded headset? I've always avoided cases that require fork 
>>> removal.
>>>
>>> On Mon, Jul 24, 2023 at 8:40 AM Chasen Smith  
>>> wrote:
>>>
 Going off of what Piaw said of the AHH, the fact that the roadini will 
 fit in my post transfer case was a huge factor in my decision to get one! 

 On Mon, Jul 24, 2023 at 10:47 AM Piaw Na  wrote:

> Let me break down the road bike selection from Rivendell:
>
> Sam: I refuse to consider this a road bike since it doesn't take 
> sidepull calipers. :-) I've always hated both cantilever and v-brakes, 
> having experienced many reliability issues with them (they're probably 
> better now, but I still get PTSD from having them fall apart on me once 
> and 
> hours spent dealing with a heron that squealed like the proverbial stuck 
> pig when descending major passes in the alps). I consider even disc 
> brakes 
> to be a better compromise if you need wider tires than a Tektro 559. And 
> those squeal too just not as badly.
> Roadeo: classic road bike using medium reach brakes  I've got a 
> friend who got a Lynskey built up to match the geometry (Rivendell only 
> had 
> one demo Roadeo when he wanted to buy and the wait was such that a custom 
> Lynskey would deliver faster) and he loves it. If you don't need more 
> than 
> 35mm tires it's a great bike.
> Roadini: gravelish bike with Tektro brakes that can take 42mm tires. 
> The higher BB means you can't treat it like a MTB and never have a pedal 
> strike no matter what trails you ride on. It's versatile and heavier but 
> a 
> reasonable compromise.
> AHH: fully lugged road bike with a low BB built for tires wider than 
> 30mm. The ultra long chainstays means it's suitable for even rougher 
> trails 
> than the Roadini but might also mean it's harder to fly with. The 135mm 
> rear wheel is strong enough to handle anything a MTB can. With good bike 
> handling skills and 45mm tires this would be my choice for bikepacking 
> (though I'm light enough the Roadini will serve well there).
>
> On Monday, July 24, 2023 at 7:39:03 AM UTC-7 Piaw Na wrote:
>
>> Oh yeah, the AHH doesn't have downtube shifter bosses, while the 
>> Roadini does. Again, a minor consideration --- I'm happy with my 
>> downtube 
>> shifter on my Roadini, but it wouldn't have killed me to go to bar-end 
>> shifters.
>>
>> On Monday, July 24, 2023 at 7:35:31 AM UTC-7 Piaw Na wrote:
>>
>>> The AHH has 50cm chainstays, which might make it hard to fit into my 
>>> bike box for flying (I use a Trico-Ironcase). The AHH also takes 135mm 
>>> rear 
>>> wheels, while the wheels I had hanging in the garage were all 130mm 
>>> wheels. 
>>> Grant advised against cold setting an AHH. In exchange the Roadini has 
>>> a 
>>> 5mm higher BB, which I dislike (others claim you can't tell the 
>>> difference 
>>> but I can, from having ridden an 80mm drop touring bike for many 
>>> years), 
>>> but something I'm willing to trade. If my current custom touring bike 
>>> fails, I'll go for a custom bike with the Roadini geometry but with an 
>>> 80 
>>> or even 85mm BB drop now that I'm unlikely to ride tires narrower than 
>>> 28mm.
>>>
>>> That's 

Re: [RBW] Re: ISO Roadini...or?

[Wesley]

In my opinion, the most significant difference between a Roadini and a 
homer is that the Roadini is designed for drop bars (so has a shorter top 
tube) and the Homer is designed for upright swept-back bars.

On Monday, July 24, 2023 at 6:32:03 AM UTC-7 Davey Two Shoes wrote:

> Can someone explain to me what would prompt a decision for a roadini over 
> a Homer aside from price? I though the Homer was Rivs "zippy" offering. 
> With the Roadeo being their fast offering. The road bike category at Riv is 
> starting to get crowded between the Sam, Homer, Roadini and Roadeo. I know 
> Riv calls the Sam a Hilli/Gravel bike, but coming from a modern gravel 
> bike, and before that a Salsa Vaya, the Sam is definitely a road bike that 
> happens to be tough and capable elsewhere. But a Road Bike when the day is 
> done.
>
> On Monday, July 24, 2023 at 8:51:03 AM UTC-4 jrst...@gmail.com wrote:
>
>>
>> For some of us who have had back pain with more modern bikes Rivendells 
>> have always been a breath of fresh air. I started buying them in 1997 and 
>> have not looked back, they made riding possible for me again. 
>>
>> I do prefer the Rivs with the shorter for Riv  chainstays. Nice bikes for 
>> those of us who have issues with more aggressive geometries. For me not 
>> koolaide but a practical   comfort. 
>>
>> Glad your aluminum bike works for you.
>>
>>
>>
>> On Mon, Jul 24, 2023 at 2:13 AM Nick Payne  wrote:
>>
>>> On Monday, 24 July 2023 at 2:43:06 pm UTC+10 Joe Bernard wrote:
>>>
>>> Modern bikes are fine - I recommended the OP consider one as a companion 
>>> to his Sam - but being on a Rivendell group and calling us "people who've 
>>> drunk the Kool-Aid" is... interesting 
>>>
>>> I have Rivendell bikes, and they're nice bikes to ride. I just don't 
>>> think they're the be-all and end-all of bicycle design. What the OP seems 
>>> to be looking for in a bike is closer to what you and I both recommended.
>>>
>>> Nick Payne
>>>
>>> -- 
>>>
>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "RBW Owners Bunch" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/rbw-owners-bunch/tAas6urcOwg/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> rbw-owners-bun...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/rbw-owners-bunch/13882503-75a4-40f2-9d54-176ca8afa9a8n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/f8ffeb68-46f9-4eaa-bbf6-28056494e281n%40googlegroups.com.

Re: SSH Error in libcrypto

[Wesley Kerfoot]

You should check that your hard drive isn't failing before reinstalling
everything. That sounds like a symptom of a bad disk if multiple files are
empty that shouldn't be.

On Sat, Jul 22, 2023, 9:41 AM Silvio Siefke  wrote:

>
>
> Am 22.07.23 um 15:23 schrieb Martin Rys:
> > What's the output of `file ~/.ssh/siefke_key; ls -lah ~/.ssh/siefke_key`?
> >
>
> All 0 byte files. Much 0 byte files. I not understand what happen here
> but I think I need to reinstall Arch Linux.
>
> Silvio
>

[RBW] Re: Ebike Clem

[Wesley]

I was not aware that you can do a mid-drive conversion (I thought the frame 
had to be special designed to accept the drive-unit instead of a bottom 
bracket). How did you do it?
-Wes
On Monday, July 17, 2023 at 11:03:34 AM UTC-7 Joe Bernard wrote:

> Looks like you're good there, Stephen, 250W is pretty mellow. Yes it's the 
> torque that would concern me with a more powerful hub motor; no bad 
> experiences (I used 250W on an Appaloosa), I just try not to be too crazy 
> with slim fork blades not designed with a motor in mind. Most 
> front-hub-motor bikes I see are running really beefy forks. 
>
> My first build was a ridiculously powerful rear-hub Clem, Grant rode it! 
> Then I did a few with even more ridiculously powerful mid-drives, those 
> were tons of fun. But I'm out of the ebike game these days. Maybe in the 
> future I'll try one again. 
>
> Joe Bernard 
>
> On Monday, July 17, 2023 at 6:46:52 AM UTC-7 Stephen wrote:
>
>> Hey Joe,
>>
>> That would be because of too much torque on a weak fork I presume? I'd be 
>> curious to hear more about your experiences with eRivs, and is that a 
>> determination you've made based on a bad experience? Have you done both 
>> front and rear type motors? I have to admit I'm pretty clueless when it 
>> comes to the details of ebikes in general, but I hope that since this kit 
>> is intended to be universal it will be safe enough for the type of riding 
>> my father will be doing and that the company would be responsible enough to 
>> highlight potential incompatibilities. It does seem like eBikes are still a 
>> bit of a wild west of little to no regulation.. Unfortunately the kit 
>> website is pretty limited in describing its technical specifications (it is 
>> very much designed for non technical people) and I can't find a spec as to 
>> whether its a 250w or 500w motor, but it does list a 40nm torque. How does 
>> that speak to your experience?
>>
>> I didn't notice anything bad on my test ride yesterday, but I suppose 
>> I'll give it a longer ride today and see if I notice any dangerous fork 
>> flex...
>>
>> On Sunday, July 16, 2023 at 10:02:46 PM UTC-4 Joe Bernard wrote:
>>
>>> Looks fun but - as a fellow who's built a few eRivs - I gotta throw in a 
>>> warning here about wattage. If that's a 250W hub you're good, I would worry 
>>> about 500W on Riv's spindly forks. 
>>>
>>> On Sunday, July 16, 2023 at 4:33:14 PM UTC-7 Stephen wrote:
>>>
 Thought I'd share my project of the day: electrifying this clem L for 
 my Dad.

 A little backstory:

 My family and I all chipped in a few years ago to get my Dad a Clem 
 complete in an effort to give him a fun and healthy exercise activity 
 following a near death heart attack in 2020. Despite really liking the 
 look 
 and comfort of the bike, his level of fitness was really limiting the 
 amount of time he could spend on it. He'd be wiped in under 30 minutes, 
 and 
 unfortunately living in the suburban south, safe and accessible riding is 
 fairly limited and largely unexciting unless you're covering big miles out 
 on country roads. Add to that the fact that his main riding partner, my 
 mom, has been a long time road cyclist with a much higher level of 
 fitness, 
 they ended up getting him an ebike from rei. Its made a huge difference in 
 how much he's able to ride and his willingness to ride, but he's still 
 been 
 partial towards the Clem. 

 So my folks ordered an ebike conversion kit, gosh, like a year ago and 
 it finally arrived recently. Its a front wheel motor with a handlebar 
 mounted battery pack, and supposedly a pretty simple install. However, for 
 some reason the axle on the wheel was 10mm as opposed to the 9mm clem fork 
 drop outs so I had to do a bit of filing (on the axle) to get it to fit. 
 Took it for a spin and it really goes! Feels a little less 
 jarring/unnatural than other ebikes I've tried. I'm curious to see how it 
 holds up.

 Please excuse the messy cables in the pics, still got some neatening up 
 to do. And for those curious, the kit is the swytch bike kit.

 [image: IMG_5909.jpg]

 [image: IMG_5910.jpg]

 [image: IMG_5911.jpg]

 [image: IMG_5912.jpg]

>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/501839fe-51b8-4af5-8bec-0f04d9d41e63n%40googlegroups.com.

[ceph-users] Re: librbd hangs during large backfill

[Wesley Dillingham]

Did your automation / process allow for stalls in between changes to allow
peering to complete? My hunch is you caused a very large peering storm
(during peering a PG is inactive) which in turn caused your VMs to panic.
If the RBDs are unmapped and re-mapped does it still continue to struggle?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, Jul 18, 2023 at 11:52 AM <
fb2cd0fc-933c-4cfe-b534-93d67045a...@simplelogin.com> wrote:

> Starting on Friday, as part of adding a new pod of 12 servers, we
> initiated a reweight on roughly 384 drives; from 0.1 to 0.25. Something
> about the resulting large backfill is causing librbd to hang, requiring
> server restarts. The volumes are showing buffer i/o errors when this
> happens.We are currently using hybrid OSDs with both SSD and traditional
> spinning disks. The current status of the cluster is:
> ceph --version
> ceph version 14.2.22
> Cluster Kernel 5.4.49-200
> {
> "mon": {
> "ceph version 14.2.22 nautilus (stable)": 3
> },
> "mgr": {
> "ceph version 14.2.22 nautilus (stable)": 3
> },
> "osd": {
> "ceph version 14.2.21 nautilus (stable)": 368,
> "ceph version 14.2.22 (stable)": 2055
> },
> "mds": {},
> "rgw": {
> "ceph version 14.2.22 (stable)": 7
> },
> "overall": {
> "ceph version 14.2.21 (stable)": 368,
> "ceph version 14.2.22 (stable)": 2068
> }
> }
>
> HEALTH_WARN, noscrub,nodeep-scrub flag(s) set.
> pgs: 6815703/11016906121 objects degraded (0.062%) 2814059622/11016906121
>  objects misplaced (25.543%).
>
> The client servers are on 3.10.0-1062.1.2.el7.x86_6
>
> We have found a couple of issues that look relevant:
> https://tracker.ceph.com/issues/19385
> https://tracker.ceph.com/issues/18807
> Has anyone experienced anything like this before? Does anyone have any
> recommendations as to settings that can help alleviate this while the
> backfill completes?
> An example of the buffer ii/o errors:
>
> Jul 17 06:36:08 host8098 kernel: buffer_io_error: 22 callbacks suppressed
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 0, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-4, logical
> block 3, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-5, logical
> block 511984, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-6, logical
> block 3487657728, async page read
> Jul 17 06:36:08 host8098 kernel: Buffer I/O error on dev dm-6, logical
> block 3487657729, async page read
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: mon log file grows huge

[Wesley Dillingham]

At what level do you have logging set to for your mons? That is a high
volume of logs for the mon to generate.

You can ask all the mons to print their debug logging level with:

"ceph tell mon.* config get debug_mon"

The default is 1/5

What is the overall status of your cluster? Is it healthy?

"ceph status"

Consider implementing more aggressive log rotation

This link may provide useful
https://docs.ceph.com/en/latest/rados/troubleshooting/log-and-debug/



Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Jul 10, 2023 at 9:44 AM Ben  wrote:

> Hi,
>
> In our cluster monitors' log grows to couple GBs in days. There are quite
> many debug message from rocksdb, osd, mgr and mds. These should not be
> necessary with a well-run cluster. How could I close these logging?
>
> Thanks,
> Ben
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Bug#1040172: mailman3: manage.py migrate not run on upgrade

[Wesley Hertlein]

Package: mailman3
Version: 3.3.8-1
Severity: normal

Dear Maintainer,

I ran into a problem on upgrading an installation of mailman3 during
a Debian system update from bullseye to bookworm.

After the upgrade, the default/installed cron jobs at the hour level
started throwing errors:

[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly 
/usr/share/mailman3-web/manage.py runjobs hourly

[ERROR/MainProcess] Failed indexing 1 - 1 (retry 5/5): (1054, "Unknown column 
'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'") (pid 2307): 
(1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 
'field list'")
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 173, in __get__
rel_obj = self.field.get_cached_value(instance)
  ^
  File "/usr/lib/python3/dist-packages/django/db/models/fields/mixins.py", line 
15, in get_cached_value
return instance._state.fields_cache[cache_name]
   
KeyError: 'mailinglist'

I got a similar error in the logs when I tried to use the web UI to
poke around the hyperkitty settings.  After some random websearches I
took a guess and ran:

# cd /usr/share/mailman3-web
# python3 manage.py migrate
Operations to perform:
  Apply all migrations: account, admin, auth, contenttypes, django_mailman3, 
django_q, hyperkitty, postorius, sessions, sites, socialaccount
Running migrations:
  Applying auth.0012_alter_user_first_name_max_length... OK
  Applying django_q.0010_auto_20200610_0856... OK
  Applying django_q.0011_auto_20200628_1055... OK
  Applying django_q.0012_auto_20200702_1608... OK
  Applying django_q.0013_task_attempt_count... OK
  Applying django_q.0014_schedule_cluster... OK
  Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK
  Applying hyperkitty.0023_alter_mailinglist_name... OK

Running this resolved the errors.  It's possible the problem here was on
my end (as noted by `mailman3/dbconfig-install: false` in this report) -
the dpkg configuration question sounded like I should choose 'no' if I
had previously set up a database, which of course coming from a working
bullseye installation I had.

Ideally this would have run as part of the package upgrade.

I also got a number of warnings that I was able to clean up easily
enough, this was the only hard error that appeared to break
functionality.  Let me know if there is interest and I can file bugs for
those.  It's possible/probable that they've been dealt with upstream -
this felt like the only Debian specific issue.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailman3 depends on:
ii  cron 3.0pl1-162
ii  dbconfig-mysql   2.0.24
ii  debconf [debconf-2.0]1.5.82
ii  init-system-helpers  1.65.2
ii  logrotate3.21.0-1
ii  python3  3.11.2-1+b1
ii  python3-aiosmtpd 1.4.3-1.1
ii  python3-alembic  1.8.1-2
ii  python3-authheaders  0.15.2-1
ii  python3-authres  1.2.0-3
ii  python3-click8.1.3-2
ii  python3-dateutil 2.8.2-2
ii  python3-dnspython2.3.0-1
ii  python3-falcon   3.1.1-1+b1
ii  python3-flufl.bounce 4.0-3
ii  python3-flufl.i18n   3.0.1-3
ii  python3-flufl.lock   5.0.1-4
ii  python3-gunicorn 20.1.0-6
ii  python3-importlib-resources  5.1.2-2
ii  python3-lazr.config  2.2.3-3
ii  python3-passlib  1.7.4-3
ii  python3-psycopg2 2.9.5-1+b1
ii  python3-public   2.3-4
ii  python3-pymysql  1.0.2-2
ii  python3-requests 2.28.1+dfsg-1
ii  python3-sqlalchemy   1.4.46+ds1-1
ii  python3-zope.component   5.1.0-1
ii  python3-zope.configuration   4.4.1-1
ii  python3-zope.event   4.4-3
ii  python3-zope.interface   5.5.2-1+b1
ii  ucf  3.0043+nmu1

Versions of packages mailman3 recommends:
ii  postfix [mail-transport-agent]  3.7.5-2

Versions of packages mailman3 suggests:
pn  anacron
ii  default-mysql-server   1.1.0
ii  lynx [www-browser] 2.9.0dev.12-1
ii  mailman3-doc   3.3.8-1
ii  mariadb-server [virtual-mysql-server]  1:10.11.3-1

-- debconf information:
  mailman3/database-type: mysql
  mailman3/upgrade-error: abort
  mailman3/mysql/authplugin: default
  

[ceph-users] Re: ceph.conf and two different ceph clusters

[Wesley Dillingham]

You need to use the --id and --cluster options of the rbd command and
maintain a .conf file for each cluster.

/etc/ceph/clusterA.conf
/etc/ceph/clusterB.conf

/etc/ceph/clusterA.client.userA.keyring
/etc/ceph/clusterB.client.userB.keyring

now use the rbd commands as such:

rbd --id userA --cluster clusterA

This will cause the client to read the appropriate files (
/etc/ceph/clusterA.client.userA.keyring and  /etc/ceph/clusterA.conf)
The --id and --cluster translate to which file is read for config and
keyring


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Jun 26, 2023 at 9:15 AM garcetto  wrote:

> good afternoon,
>   how can i config ceph.conf file on a generic rbd client to say to use two
> different ceph clusters to access different volumes on them?
>
> ceph-cluster-left --> rbd-vol-green
> ceph-cluster-right --> rbd-vol-blue
>
> thank you.
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[spring] Tsvart last call review of draft-ietf-spring-sr-replication-segment-14

[Wesley Eddy via Datatracker]

Reviewer: Wesley Eddy
Review result: Almost Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-...@ietf.org if you reply to or forward this review.

(1) Since this defines a behavior where one incoming packet can create N
outgoing packets, I was surprised that there is nothing mentioned in the
security considerations about how access to replication nodes and ingress for
them should be protected in order to prevent abuse.

(2) The intended use seems mainly to be where some outer control system is
responsible for making sure that the replication operation will put packets
onto distinct network paths, and not create congestion either locally or on
some potential shared network segment downstream.  It might be more clearly
stated that it's assumed that building a proper multicast tree, managing group
membership, and performing multicast congestion control need to be performed
elsewhere.

(3) I didn't recognize the syntax or pseudocode conventions in section 2.2.1;
maybe this is common or defined somewhere else that could be referenced to be
clear?


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[Mpi-forum] 2023-06-14 Non-Voting Meeting and 2023-07-10 Voting Meeting Reminders

[Wesley Bland via mpi-forum]

Hi all,

A few quick reminders:

1. We have a non-voting meeting tomorrow (2023-06-14) where Rolf will continue 
the discussions from last week and we'll cover any other MPI 4.1 topics as we 
hurtle toward release.

2. The announcement deadline for the July meeting is coming up on June 26. 
Please remember to announce any votes and/or readings before that date. All of 
the items on this board are expected for MPI 4.1, but have not yet been 
announced (as far as I'm aware): 
https://github.com/orgs/mpi-forum/projects/1/views/9.

3. Registration for the upcoming July meeting is open. If you're not sure if 
you've registered, you can find that here: 
https://www.mpi-forum.org/meetings/2023/07/attendance. If you haven't 
registered, you can do that here: https://forms.gle/rLseYfaUB9msiB4E9.

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [RBW] ISO Better Bar-End Friction Shifting!

[Wesley]

Caroline,
If you recently had the chain and cassette replace, then your problems with 
the chain dropping may be because the chainring is worn. Most chainrings 
are aluminum, which wears faster than steel cogs. And since the same 
chainring is used for all riding while the cogs are changed by shifting, 
the wear is more concentrated on the chainring. Both of these lead to 
chainrings wiring out faster than cogs, and a worn chainring will not hold 
the chain securely. This can act in combination with problems others hav 
suggested here - especially bent detailer hanger and too-slack chain - to 
drop the chain off the chainring.
-Wes

On Thursday, June 8, 2023 at 10:53:07 AM UTC-7 Caroline Golum wrote:

> Thanks everyone! I had the chain + cassette replaced in February, both new 
> parts, so I'm assuming they both have plenty of life left. 
>
> The last mechanic I spoke with assured me the limits on my derailleur were 
> good. FWIW I've had the same Shimano 105 rear derailleur since I built the 
> bike in 2009. 
>
> On Thursday, June 8, 2023 at 1:42:45 PM UTC-4 lconley wrote:
>
>> Did the derailleur service include verification that the derailleur 
>> hanger is straight?
>>
>> Agree that it is unlikely to be a shifter issue.
>>
>> Laing
>>
>> On Thursday, June 8, 2023 at 1:34:54 PM UTC-4 eliot...@gmail.com wrote:
>>
>>> That sounds like an issue with chain retention and not the shifter. 
>>> Clutch RD ? New rings ? New chain ?
>>>
>>> On Thu, Jun 8, 2023 at 10:32 AM Caroline Golum  
>>> wrote:
>>>
 Currently running 1x10 and friction bar-end shifting. The chain keeps 
 coming off my crank, not hitting the right gear in the rear, etc. I've had 
 the derailleur serviced, it's fine, etc. 

 Time to get a new shifter? Switch to indexed shifting? Switch to an 
 8/9spd in the rear? The bar-end shifter is RBW's Shifter - Silver2 
 .  

 -- 
 You received this message because you are subscribed to the Google 
 Groups "RBW Owners Bunch" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to rbw-owners-bun...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/rbw-owners-bunch/665b64a1-dea4-47b8-8417-d2b1ce26392bn%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/ebfa1cdd-d63a-42ed-ab25-dc0ce4abd6e1n%40googlegroups.com.

[ceph-users] Re: The pg_num from 1024 reduce to 32 spend much time, is there way to shorten the time？

[Wesley Dillingham]

Can you send along the responses from "ceph df detail" and ceph "ceph osd
pool ls detail"

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, Jun 6, 2023 at 1:03 PM Eugen Block  wrote:

> I suspect the target_max_misplaced_ratio (default 0.05). You could try
> setting it to 1 and see if it helps. This has been discussed multiple
> times on this list, check out the archives for more details.
>
> Zitat von Louis Koo :
>
> > Thanks for your responses, I want to know why it spend much time to
> > reduce the pg num?
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
>
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: PGs stuck undersized and not scrubbed

[Wesley Dillingham]

When PGs are degraded they won't scrub, further, if an OSD is involved with
recovery of another PG it wont accept scrubs either so that is the likely
explanation of your not-scrubbed-in time issue. Its of low concern.

Are you sure that recovery is not progressing? I see: "7349/147534197
objects degraded" can you check that again (maybe wait an hour) and see if
7,349 has been reduced.

Another thing I'm noticing is that OSD 57 and 79 are the primary for many
of the PGs which are degraded. They might could use a service restart.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, Jun 5, 2023 at 12:01 PM Nicola Mori  wrote:

> Dear Ceph users,
>
> after an outage and recovery of one machine I have several PGs stuck in
> active+recovering+undersized+degraded+remapped. Furthermore, many PGs
> have not been (deep-)scrubbed in time. See below for status and health
> details.
> It's been like this for two days, with no recovery I/O being reported,
> so I guess something is stuck in a bad state. I'd need some help in
> understanding what's going on here and how to fix it.
> Thanks,
>
> Nicola
>
> -
>
> # ceph -s
>cluster:
>  id: b1029256-7bb3-11ec-a8ce-ac1f6b627b45
>  health: HEALTH_WARN
>  2 OSD(s) have spurious read errors
>  Degraded data redundancy: 7349/147534197 objects degraded
> (0.005%), 22 pgs degraded, 22 pgs undersized
>  332 pgs not deep-scrubbed in time
>  503 pgs not scrubbed in time
>  (muted: OSD_SLOW_PING_TIME_BACK OSD_SLOW_PING_TIME_FRONT)
>
>services:
>  mon: 5 daemons, quorum bofur,balin,aka,romolo,dwalin (age 2d)
>  mgr: bofur.tklnrn(active, since 32h), standbys: balin.hvunfe,
> aka.wzystq
>  mds: 2/2 daemons up, 1 standby
>  osd: 104 osds: 104 up (since 37h), 104 in (since 37h); 22 remapped pgs
>
>data:
>  volumes: 1/1 healthy
>  pools:   3 pools, 529 pgs
>  objects: 18.53M objects, 40 TiB
>  usage:   54 TiB used, 142 TiB / 196 TiB avail
>  pgs: 7349/147534197 objects degraded (0.005%)
>   2715/147534197 objects misplaced (0.002%)
>   507 active+clean
>   20  active+recovering+undersized+degraded+remapped
>   2   active+recovery_wait+undersized+degraded+remapped
>
> # ceph health detail
> [WRN] PG_DEGRADED: Degraded data redundancy: 7349/147534197 objects
> degraded (0.005%), 22 pgs degraded, 22 pgs undersized
>  pg 3.2c is stuck undersized for 37h, current state
> active+recovery_wait+undersized+degraded+remapped, last acting
> [79,83,34,37,65,NONE,18,95]
>  pg 3.57 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,99,37,NONE,15,104,55,40]
>  pg 3.76 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,5,37,15,100,33,85,NONE]
>  pg 3.9c is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,86,88,NONE,11,69,20,10]
>  pg 3.106 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [79,15,89,NONE,36,32,23,64]
>  pg 3.107 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [79,NONE,64,20,61,92,104,43]
>  pg 3.10c is stuck undersized for 37h, current state
> active+recovery_wait+undersized+degraded+remapped, last acting
> [79,34,NONE,95,104,16,69,18]
>  pg 3.11e is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [79,89,64,46,32,NONE,40,15]
>  pg 3.14e is stuck undersized for 37h, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,34,69,97,85,NONE,46,62]
>  pg 3.160 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,1,101,84,18,33,NONE,69]
>  pg 3.16a is stuck undersized for 37h, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,16,59,103,13,38,49,NONE]
>  pg 3.16e is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,0,27,96,55,10,81,NONE]
>  pg 3.170 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [NONE,57,14,46,55,99,15,40]
>  pg 3.19b is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [NONE,79,59,8,32,17,7,90]
>  pg 3.1a0 is stuck undersized for 2d, current state
> active+recovering+undersized+degraded+remapped, last acting
> [NONE,79,26,50,104,24,97,40]
>  pg 3.1a5 is stuck undersized for 37h, current state
> active+recovering+undersized+degraded+remapped, last acting
> [57,100,61,27,20,NONE,24,85]
>  pg 3.1a8 is stuck undersized for 2d, current state
>