This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] USB drive
- Previous message (by thread): [atlas] USB drive
- Next message (by thread): [atlas] Plan to Implement RIPE Atlas WiFi Measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Ionescu
mhi at ionescu.de
Wed Mar 30 14:54:40 CEST 2016
Hi Philip, thanks for clearing this up. It would be really great to take some of the guesswork out of these cases, by adding one or two checks regarding the thumbdrive and file system status, transmitting negative results via descriptive SOS messages and/or system status tags. On my probe the USB problems led to a system tag "Firewall problem suspected". This is quite misleading. After your description I would suspect the FS issue impeded the probe so deeply that it wasn't able to call home at all anymore. To my understanding, probes should be fire-and-forget as much as possible, so I think any fsck should be run in a way that would not impede an otherwise functioning probe. Michael On 30.03.2016 13:50, Philip Homburg wrote: > Hi Michael, > [...] > In general, the probe doesn't care what is on the USB stick. So wiping > or formatting the stick is not needed. > > There is at the moment one rare exception. The filesystem can go corrupt > to the point the fsck hangs. > [...] > Philip
- Previous message (by thread): [atlas] USB drive
- Next message (by thread): [atlas] Plan to Implement RIPE Atlas WiFi Measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]