Documentation/kmsg/s390/dasd

   1 /* dasd_ioctl */
   2
   3 /*?
   4  * Text: "%s: The DASD has been put in the quiesce state\n"
   5  * Severity: Informational
   6  * Parameter:
   7  *   @1: bus ID of the DASD
   8  * Description:
   9  * No I/O operation is possible on this device.
  10  * User action:
  11  * Resume the DASD to enable I/O operations.
  12  */
  13
  14 /*?
  15  * Text: "%s: I/O operations have been resumed on the DASD\n"
  16  * Severity: Informational
  17  * Parameter:
  18  *   @1: bus ID of the DASD
  19  * Description:
  20  * The DASD is no longer in state quiesce and I/O operations can be performed
  21  * on the device.
  22  * User action:
  23  * None.
  24  */
  25
  26 /*?
  27  * Text: "%s: The DASD cannot be formatted while it is enabled\n"
  28  * Severity: Warning
  29  * Parameter:
  30  *   @1: bus ID of the DASD
  31  * Description:
  32  * The DASD you try to format is enabled. Enabled devices cannot be formatted.
  33  * User action:
  34  * Contact the owner of the formatting tool.
  35  */
  36
  37 /*?
  38  * Text: "%s: The specified DASD is a partition and cannot be formatted\n"
  39  * Severity: Warning
  40  * Parameter:
  41  *   @1: bus ID of the DASD
  42  * Description:
  43  * The DASD you try to format is a partition. Partitions cannot be formatted
  44  * separately. You can only format a complete DASD including all its partitions.
  45  * User action:
  46  * Format the complete DASD.
  47  * ATTENTION: Formatting irreversibly destroys all data on all partitions
  48  * of the DASD.
  49  */
  50
  51 /*?
  52  * Text: "%s: The specified DASD is a partition and cannot be checked\n"
  53  * Severity: Warning
  54  * Parameter:
  55  *   @1: bus ID of the DASD
  56  * Description:
  57  * The DASD you try to check is a partition. Partitions cannot be checked
  58  * separately. You can only check a complete DASD including all its partitions.
  59  * User action:
  60  * Check the complete DASD.
  61  */
  62
  63 /*?
  64  * Text: "%s: Formatting unit %d failed with rc=%d\n"
  65  * Severity: Error
  66  * Parameter:
  67  *   @1: bus ID of the DASD
  68  *   @2: start track
  69  *   @3: return code
  70  * Description:
  71  * The formatting process might have been interrupted by a signal, for example,
  72  * CTRL+C. If the process was not interrupted intentionally, an I/O error
  73  * might have occurred.
  74  * User action:
  75  * Retry to format the device. If the error persists, check the log file for
  76  * related error messages. If you cannot resolve the error, note the return
  77  * code and contact your support organization.
  78  */
  79
  80
  81 /* dasd */
  82
  83 /*?
  84  * Text: "%s: Cancelling request %p failed with rc=%d\n"
  85  * Severity: Error
  86  * Parameter:
  87  *   @1: bus ID of the DASD
  88  *   @2: pointer to request
  89  *   @3: return code of previous function
  90  * Description:
  91  * In response to a user action, the DASD device driver tried but failed to
  92  * cancel a previously started I/O operation.
  93  * User action:
  94  * Try the action again.
  95  */
  96
  97 /*?
  98  * Text: "%s: Flushing the DASD request queue failed for request %p\n"
  99  * Severity: Error
 100  * Parameter:
 101  *   @1: bus ID of the DASD
 102  *   @2: pointer to request
 103  * Description:
 104  * As part of the unloading process, the DASD device driver flushes the
 105  * request queue. This failed because a previously started I/O operation
 106  * could not be canceled.
 107  * User action:
 108  * Try again to unload the DASD device driver or to shut down Linux.
 109  */
 110
 111 /*?
 112  * Text: "The DASD device driver could not be initialized\n"
 113  * Severity: Informational
 114  * Description:
 115  * The initialization of the DASD device driver failed because of previous
 116  * errors.
 117  * User action:
 118  * Check for related previous error messages.
 119  */
 120
 121 /*?
 122  * Text: "%s: Accessing the DASD failed because it is in probeonly mode\n"
 123  * Severity: Informational
 124  * Parameter:
 125  *   @1: bus ID of the DASD
 126  * Description:
 127  * The dasd= module or kernel parameter specified the probeonly attribute for
 128  * the DASD you are trying to access. The DASD device driver cannot access
 129  * DASDs that are in probeonly mode.
 130  * User action:
 131  * Change the dasd= parameter as to omit probeonly for the DASD and reload
 132  * the DASD device driver. If the DASD device driver has been compiled into
 133  * the kernel, reboot Linux.
 134  */
 135
 136 /*?
 137  * Text: "%s: cqr %p timed out (%lus), %i retries remaining\n"
 138  * Severity: Error
 139  * Parameter:
 140  *   @1: bus ID of the DASD
 141  *   @2: request
 142  *   @3: timeout value
 143  *   @4: number of retries left
 144  * Description:
 145  * A try of the error recovery procedure (ERP) for the channel queued request
 146  * (cqr) timed out and failed to recover the error. ERP continues for the DASD.
 147  * User action:
 148  * Ignore this message if it occurs infrequently and if the recovery succeeds
 149  * during one of the retries. If this error persists, check for related
 150  * previous error messages and report the problem to your support organization.
 151  *
 152  * The timeout can be changed by writing a new value to the sysfs 'expires' attribute of the DASD. The value specifies the timeout in seconds.
 153  */
 154
 155 /*?
 156  * Text: "%s: cqr %p timed out (%lus) but cannot be ended, retrying in 5 s\n"
 157  * Severity: Error
 158  * Parameter:
 159  *   @1: bus ID of the DASD
 160  *   @2: request
 161  *   @3: timeout value
 162  * Description:
 163  * A try of the error recovery procedure (ERP) for the channel queued request
 164  * (cqr) timed out and failed to recover the error. The I/O request submitted
 165  * during the try could not be canceled. The ERP waits for 5 seconds before
 166  * trying again.
 167  * User action:
 168  * Ignore this message if it occurs infrequently and if the recovery succeeds
 169  * during one of the retries. If this error persists, check for related
 170  * previous error messages and report the problem to your support organization.
 171  *
 172  * The timeout can be changed by writing a new value to the sysfs 'expires' attribute of the DASD. The value specifies the timeout in seconds.
 173  */
 174
 175 /*?
 176  * Text: "%s: The DASD cannot be set offline while it is in use\n"
 177  * Severity: Warning
 178  * Parameter:
 179  *   @1: bus ID of the DASD
 180  * Description:
 181  * The DASD cannot be set offline because it is in use by an internal process.
 182  * An action to free the DASD might not have completed yet.
 183  * User action:
 184  * Wait some time and set the DASD offline later.
 185  */
 186
 187 /*?
 188  * Text: "%s: The DASD cannot be set offline with open count %i\n"
 189  * Severity: Warning
 190  * Parameter:
 191  *   @1: bus ID of the DASD
 192  *   @2: count
 193  * Description:
 194  * The DASD is being used by one or more processes and cannot be set offline.
 195  * User action:
 196  * Ensure that the DASD is not in use anymore, for example, unmount all
 197  * partitions. Then try again to set the DASD offline.
 198  */
 199
 200 /*?
 201  * Text: "%s: Setting the DASD online failed with rc=%d\n"
 202  * Severity: Warning
 203  * Parameter:
 204  *   @1: bus ID of the DASD
 205  *   @2: return code
 206  * Description:
 207  * The DASD could not be set online because of previous errors.
 208  * User action:
 209  * Look for previous error messages. If you cannot resolve the error, note
 210  * the return code and contact your support organization.
 211  */
 212
 213 /*?
 214  * Text: "%s Setting the DASD online with discipline %s failed with rc=%i\n"
 215  * Severity: Warning
 216  * Parameter:
 217  *   @1: bus ID of the DASD
 218  *   @2: discipline
 219  *   @3: return code
 220  * Description:
 221  * The DASD could not be set online because of previous errors.
 222  * User action:
 223  * Look for previous error messages. If you cannot resolve the error, note the
 224  * return code and contact your support organization.
 225  */
 226
 227 /*?
 228  * Text: "%s Setting the DASD online failed because of missing DIAG discipline\n"
 229  * Severity: Warning
 230  * Parameter:
 231  *   @1: bus ID of the DASD
 232  * Description:
 233  * The DASD was to be set online with discipline DIAG but this discipline of
 234  * the DASD device driver is not available.
 235  * User action:
 236  * Ensure that the dasd_diag_mod module is loaded. If your Linux system does
 237  * not include this module, you cannot set DASDs online with the DIAG
 238  * discipline.
 239  */
 240
 241 /*?
 242  * Text: "%s Setting the DASD online failed because of a missing discipline\n"
 243  * Severity: Warning
 244  * Parameter:
 245  *   @1: bus ID of the DASD
 246  * Description:
 247  * The DASD was to be set online with a DASD device driver discipline that
 248  * is not available.
 249  * User action:
 250  * Ensure that all DASD modules are loaded correctly.
 251  */
 252
 253 ---------------------------
 254
 255 /*?
 256  * Text: "The statistics feature has been switched off\n"
 257  * Severity: Informational
 258  * Description:
 259  * The statistics feature of the DASD device driver has been switched off.
 260  * User action:
 261  * None.
 262  */
 263
 264 /*?
 265  * Text: "The statistics feature has been switched on\n"
 266  * Severity: Informational
 267  * Description:
 268  * The statistics feature of the DASD device driver has been switched on.
 269  * User action:
 270  * None.
 271  */
 272
 273 /*?
 274  * Text: "The statistics have been reset\n"
 275  * Severity: Informational
 276  * Description:
 277  * The DASD statistics data have been reset.
 278  * User action:
 279  * None.
 280  */
 281
 282 /*?
 283  * Text: "%s is not a supported value for /proc/dasd/statistics\n"
 284  * Severity: Warning
 285  * Parameter:
 286  *   @1: value
 287  * Description:
 288  * An incorrect value has been written to /proc/dasd/statistics.
 289  * The supported values are: 'set on', 'set off', and 'reset'.
 290  * User action:
 291  * Write a supported value to /proc/dasd/statistics.
 292  */
 293
 294 /*?
 295  * Text: "%s is not a valid device range\n"
 296  * Severity: Error
 297  * Parameter:
 298  *   @1: range
 299  * Description:
 300  * A device range specified with the dasd= parameter is not valid.
 301  * User action:
 302  * Examine the dasd= parameter and correct the device range.
 303  */
 304
 305 /*?
 306  * Text: "The probeonly mode has been activated\n"
 307  * Severity: Informational
 308  * Description:
 309  * The probeonly mode of the DASD device driver has been activated. In this
 310  * mode the device driver rejects any 'open' syscalls with EPERM.
 311  * User action:
 312  * None.
 313  */
 314
 315 /*?
 316  * Text: "The IPL device is not a CCW device\n"
 317  * Severity: Error
 318  * Description:
 319  * The value for the dasd= parameter contains the 'ipldev' keyword. During
 320  * the boot process this keyword is replaced with the device from which the
 321  * IPL was performed. The 'ipldev' keyword is not valid if the IPL device is
 322  * not a CCW device.
 323  * User action:
 324  * Do not specify the 'ipldev' keyword when performing an IPL from a device
 325  * other than a CCW device.
 326  */
 327
 328 /*?
 329  * Text: "A closing parenthesis ')' is missing in the dasd= parameter\n"
 330  * Severity: Warning
 331  * Description:
 332  * The specification for the dasd= kernel or module parameter has an opening
 333  * parenthesis '(' * without a matching closing parenthesis ')'.
 334  * User action:
 335  * Correct the parameter value.
 336  */
 337
 338 /*?
 339  * Text: "The autodetection mode has been activated\n"
 340  * Severity: Informational
 341  * Description:
 342  * The autodetection mode of the DASD device driver has been activated. In
 343  * this mode the DASD device driver sets all detected DASDs online.
 344  * User action:
 345  * None.
 346  */
 347
 348 /*?
 349  * Text: "%*s is not a supported device option\n"
 350  * Severity: Warning
 351  * Parameter:
 352  *   @1: length of option code
 353  *   @2: option code
 354  * Description:
 355  * The dasd= parameter includes an unknown option for a DASD or a device range.
 356  * Options are specified in parenthesis and immediately follow a device or
 357  * device range.
 358  * User action:
 359  * Check the dasd= syntax and remove any unsupported options from the dasd=
 360  * parameter specification.
 361  */
 362
 363 /*?
 364  * Text: "PAV support has be deactivated\n"
 365  * Severity: Informational
 366  * Description:
 367  * The 'nopav' keyword has been specified with the dasd= kernel or module
 368  * parameter. The Parallel Access Volume (PAV) support of the DASD device
 369  * driver has been deactivated.
 370  * User action:
 371  * None.
 372  */
 373
 374 /*?
 375  * Text: "'nopav' is not supported on z/VM\n"
 376  * Severity: Informational
 377  * Description:
 378  * For Linux instances that run as guest operating systems of the z/VM
 379  * hypervisor Parallel Access Volume (PAV) support is controlled by z/VM not
 380  * by Linux.
 381  * User action:
 382  * Remove 'nopav' from the dasd= module or kernel parameter specification.
 383  */
 384
 385 /*?
 386  * Text: "High Performance FICON support has been deactivated\n"
 387  * Severity: Informational
 388  * Description:
 389  * The 'nofcx' keyword has been specified with the dasd= kernel or module
 390  * parameter. The High Performance FICON (transport mode) support of the DASD
 391  * device driver has been deactivated.
 392  * User action:
 393  * None.
 394  */
 395
 396 /*?
 397  * Text: "The dasd= parameter value %s has an invalid ending\n"
 398  * Severity: Warning
 399  * Parameter:
 400  *   @1: parameter value
 401  * Description:
 402  * The specified value for the dasd= kernel or module parameter is not correct.
 403  * User action:
 404  * Check the module or the kernel parameter.
 405  */
 406
 407 /*?
 408  * Text: "Registering the device driver with major number %d failed\n"
 409  * Severity: Warning
 410  * Parameter:
 411  *   @1: DASD major
 412  * Description:
 413  * Major number 94 is reserved for the DASD device driver. The DASD device
 414  * driver failed to register with this major number. Another device driver
 415  * might have used major number 94.
 416  * User action:
 417  * Determine which device driver uses major number 94 instead of the DASD
 418  * device driver and unload this device driver. Then try again to load the
 419  * DASD device driver.
 420  */
 421
 422 /*?
 423   * Text: "%s: default ERP has run out of retries and failed\n"
 424   * Severity: Error
 425   * Parameter:
 426   *   @1: bus ID of the DASD
 427   * Description:
 428   * The error recovery procedure (ERP) tried to recover an error but the number
 429   * of retries for the I/O was exceeded before the error could be resolved.
 430   * User action:
 431   * Check for related previous error messages.
 432   */
 433
 434 /*?
 435  * Text: "%s: Unable to terminate request %p on suspend\n"
 436  * Severity: Error
 437  * Parameter:
 438  *   @1: bus ID of the DASD
 439  *   @2: pointer to request
 440  * Description:
 441  * As part of the suspend process, the DASD device driver terminates requests
 442  * on the request queue. This failed because a previously started I/O operation
 443  * could not be canceled. The suspend process will be stopped.
 444  * User action:
 445  * Try again to suspend the system.
 446  */
 447
 448 /*?
 449  * Text: "%s: ERP failed for the DASD\n"
 450  * Severity: Error
 451  * Parameter:
 452  *   @1: bus ID of the DASD
 453  * Description:
 454  * An error recovery procedure (ERP) was performed for the DASD but failed.
 455  * User action:
 456  * Check the message log for previous related error messages.
 457  */
 458
 459 /*?
 460  * Text: "%s: An error occurred in the DASD device driver, reason=%s\n"
 461  * Severity: Error
 462  * Parameter:
 463  *   @1: bus ID of the DASD
 464  *   @2: reason code
 465  * Description:
 466  * This problem indicates a program error in the DASD device driver.
 467  * User action:
 468  * Note the reason code and contact your support organization.
 469 */
 470
 471 /*?
 472  * Text: "%s: No operational channel path is left for the device\n"
 473  * Severity: Warning
 474  * Parameter:
 475  *   @1: bus ID of the DASD
 476  * Description:
 477  * All channel paths to the device have become non-operational. The DASD
 478  * device driver suspends I/O operations and queues I/O requests for this
 479  * device until at least one channel path becomes operational again.
 480  * User action:
 481  * Ensure that each channel path to the device has been set up correctly
 482  * and that the related physical cable connections are in place.
 483  */
 484
 485 /*?
 486  * Text: "%s: No verified channel paths remain for the device\n"
 487  * Severity: Warning
 488  * Parameter:
 489  *   @1: bus ID of the DASD
 490  * Description:
 491  * All verified channel paths to the device have become non-operational.
 492  * Any other paths to the device have previously been identified as not usable.
 493  * The DASD device driver suspends I/O operations and queues I/O requests
 494  * for this device until at least one channel path becomes operational
 495  * again.
 496  * User action:
 497  * Ensure that each channel path to the device has been set up correctly
 498  * and that the related physical cable connections are in place.
 499  * Set all paths to the device offline and online again to repeat the path
 500  * verification. Alternatively, set the device offline and online again to
 501  * verify all available paths for this device.
 502  * If this problem persists, gather Linux debug data and report the problem
 503  * to your support organization.
 504  */
 505
 506 /*?
 507  * Text: "%s: A channel path to the device has become operational\n"
 508  * Severity: Informational
 509  * Parameter:
 510  *   @1: bus ID of the DASD
 511  * Description:
 512  * At least one channel path of this device has become operational again.
 513  * The DASD device driver resumes I/O operations to the device and processes
 514  * the I/O requests that were queued while there was no operational channel path.
 515  * User action:
 516  * None.
 517  */
 518
 519 ------------------------------------------------------------------------------------
 520 /* dasd_diag */
 521
 522 /*?
 523  * Text: "%s: A 64-bit DIAG call failed\n"
 524  * Severity: Warning
 525  * Parameter:
 526  *   @1: bus ID of the DASD
 527  * Description:
 528  * 64-bit DIAG calls require a 64-bit z/VM version.
 529  * User action:
 530  * Use z/VM 5.2 or later or set the sysfs 'use_diag' attribute of the DASD to 0
 531  * to switch off DIAG.
 532  */
 533
 534 /*?
 535  * Text: "%s: Accessing the DASD failed because of an incorrect format (rc=%d)\n"
 536  * Severity: Warning
 537  * Parameter:
 538  *   @1: bus ID of the DASD
 539  *   @2: return code
 540  * Description:
 541  * The format of the DASD is not correct.
 542  * User action:
 543  * Check the device format. For details about the return code see the
 544  * section about the INITIALIZE function for DIAGNOSE Code X'250'
 545  * in "z/VM CP Programming Services". If you cannot resolve the error, note
 546  * the return code and contact your support organization.
 547  */
 548
 549 /*?
 550  * Text: "%s: New DASD with %ld byte/block, total size %ld KB%s\n"
 551  * Severity: Informational
 552  * Parameter:
 553  *   @1: bus ID of the DASD
 554  *   @2: bytes per block
 555  *   @3: size
 556  *   @4: access mode
 557  * Description:
 558  * A DASD with the indicated block size and total size has been set online.
 559  * If the DASD is configured as read-only to the real or virtual hardware,
 560  * the message includes an indication of this hardware access mode. The
 561  * hardware access mode is independent from the 'readonly' attribute of
 562  * the device in sysfs.
 563  * User action:
 564  * None.
 565  */
 566
 567 /*?
 568  * Text: "%s: DIAG ERP failed with rc=%d\n"
 569  * Severity: Warning
 570  * Parameter:
 571  *   @1: bus ID of the DASD
 572  *   @2: return code
 573  * Description:
 574  * An error in the DIAG processing could not be recovered by the error
 575  * recovery procedure (ERP) of the DIAG discipline.
 576  * User action:
 577  * Note the return code, check for related I/O errors, and report this problem
 578  * to your support organization.
 579  */
 580
 581 /*?
 582  * Text: "%s: DIAG initialization failed with rc=%d\n"
 583  * Severity: Warning
 584  * Parameter:
 585  *   @1: bus ID of the DASD
 586  *   @2: return code
 587  * Description:
 588  * Initializing the DASD with the DIAG discipline failed. Possible reasons for
 589  * this problem are that the device has a device type other than FBA or ECKD,
 590  * or has a block size other than one of the supported sizes:
 591  * 512 byte, 1024 byte, 2048 byte, or 4096 byte.
 592  * User action:
 593  * Ensure that the device can be written to and has a supported device type
 594  * and block size. For details about the return code see the section about
 595  * the INITIALIZE function for DIAGNOSE Code X'250' in "z/VM CP Programming
 596  * Services". If you cannot resolve the error, note the error code and contact
 597  * your support organization.
 598  */
 599
 600 /*?
 601  * Text: "%s: Device type %d is not supported in DIAG mode\n"
 602  * Severity: Warning
 603  * Parameter:
 604  *   @1: bus ID of the DASD
 605  *   @2: device type
 606  * Description:
 607  * Only DASD of type FBA and ECKD are supported in DIAG mode.
 608  * User action:
 609  * Set the sysfs 'use_diag' attribute of the DASD to 0 and try again to access
 610  * the DASD.
 611  */
 612
 613 /*?
 614  * Text: "Discipline %s cannot be used without z/VM\n"
 615  * Severity: Informational
 616  * Parameter:
 617  *   @1: discipline name
 618  * Description:
 619  * The discipline that is specified with the dasd= kernel or module parameter
 620  * is only available for Linux instances that run as guest operating
 621  * systems of the z/VM hypervisor.
 622  * User action:
 623  * Remove the unsupported discipline from the parameter string.
 624  */
 625
 626 /*?
 627  * Text: "%s: The access mode of a DIAG device changed to read-only\n"
 628  * Severity: Warning
 629  * Parameter:
 630  *   @1: bus ID of the DASD
 631  * Description:
 632  * A device changed its access mode from writeable to
 633  * read-only while in use.
 634  * User action:
 635  * Set the device offline, ensure that the device is configured correctly in
 636  * z/VM, then set the device online again.
 637  */
 638
 639 ------------------------------------------------------------------------------------
 640 /* dasd_erp */
 641
 642 /*?
 643  * Text: "%s: A timeout error occurred for cqr %p\n"
 644  * Severity: Error
 645  * Parameter:
 646  *   @1: bus ID of the DASD
 647  *   @2: pointer to request
 648  * Description:
 649  * A channel queued request (cqr) failed because it timed out.
 650  * One possible reason for this error is that a request did not
 651  * complete within the timeout interval specified for the DASD.
 652  * The timeout interval is set as the value of the 'timeout' sysfs
 653  * attribute of a DASD. A value of 0 disables the timeout function.
 654  * The timeout function can be used; for example, by mirroring setups;
 655  * to quickly process a request queue for a DASD that has become unavailable.
 656  * User action:
 657  * Check the message log for previous related error messages.  Verify
 658  * that the storage server and the connection from host to storage
 659  * server are operational.  If the 'timeout' sysfs attribute of the
 660  * DASD has been set to a value other than 0, verify that this
 661  * setting is intentional and change it if required.
 662  */
 663
 664 /*?
 665  * Text: "%s: A transport error occurred for cqr %p\n"
 666  * Severity: Error
 667  * Parameter:
 668  *   @1: bus ID of the DASD
 669  *   @2: pointer to request
 670  * Description:
 671  * A channel queued request (cqr) failed because the connection to the
 672  * device was lost and the 'failfast' flag is set for the request.
 673  * This flag can result from, for example:
 674  *
 675  * - A software layer above the DASD device driver;
 676  *   for example, in a host based mirroring setup.
 677  *
 678  * - Value 1 for the 'failfast' sysfs attribute of the DASD.
 679  *   This setting applies to all requests on the DASD.
 680  *
 681  * User action:
 682  * Ensure that each channel path to the device has been set up
 683  * correctly and that the related physical cable connections are in
 684  * place. If the 'failfast' attribute of the DASD is set to 1,
 685  * verify that this setting is intentional and change it to 0 if required.
 686  */
 687
 688 /*?
 689  * Text: "%s Setting the DASD online failed because the required module %s could not be loaded (rc=%d)\n"
 690  * Severity: Warning
 691  * Parameter:
 692  *   @1: bus ID of the DASD
 693  *   @2: kernel module name
 694  *   @3: return code
 695  * Description:
 696  * The DASD was to be set online with discipline DIAG but this discipline of
 697  * the DASD device driver is not available and an attempt to load the
 698  * corresponding kernel module failed with the specified return code.
 699  *
 700  * User action:
 701  * Ensure that the kernel module with the specified name is correctly installed
 702  * or set the sysfs 'use_diag' attribute of the DASD to 0 to switch off DIAG.
 703  */
 704 /*? Text: "%s: %d output lines suppressed due to ratelimiting\n" */