Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page, the default filter will display tickets relevant to you:

  • If logged in then all open tickets, it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged in and no name/email is defined in the preferences, then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the dropdown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters with either a text box or a dropdown menu of options can be added multiple times to perform an Or on the criteria.

For text fields such as Keywords and CC the - operator can be used to negate a match and double quotes (since 1.2.1) can be used to match a phrase. For example, a contains match for word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and word4 word5.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

After you have edited your filters, click the Update button to refresh your results.

Keyboard shortcuts are available for manipulating the checkbox filters:

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter. Since 1.2.1 this also works for the Columns checkboxes.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria , the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria, see Query Language.

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field>. You can specify multiple fields and what order they are displayed in by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Full rows

In table format you can also have full rows by using rows=<field>:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 1114)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1508 duplicate MKNSSDS2500GB Mark van Eck
#1501 invalid Buffer I/O error logical block async page read (TOSHIBA MQ01ABD100) 4joeyirosh1
Description

Hi!I have Debian 11 64 bit installed on my machine.

When I booted my machine today,I got the errors below during boot.Please find the output of the smartctl command below

# smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-7-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    87PSPGCKT
LU WWN Device Id: 5 000039 7f2f0a12f
Firmware Version: AX1R4C
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 12 19:55:38 2021 EAT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x86)	Offline data collection activity
					was aborted by the device with a fatal error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 199) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       1762
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3079
  5 Reallocated_Sector_Ct   0x0033   099   099   010    Pre-fail  Always       -       320
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   058   058   000    Old_age   Always       -       17022
 10 Spin_Retry_Count        0x0033   161   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2919
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1653
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   052   040    Old_age   Always       -       33 (Min/Max 28/42)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       213
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       5308497
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       5737
194 Temperature_Celsius     0x0022   067   052   040    Old_age   Always       -       33 (Min/Max 28/42)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       36
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1653 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1653 occurred at disk power-on lifetime: 17011 hours (708 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 d0 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 d8 86 f6 7f 40 00      01:02:19.290  READ FPDMA QUEUED
  60 08 d0 06 f6 7f 40 00      01:02:19.290  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:02:19.282  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 00      01:02:19.281  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:02:19.281  SET FEATURES [Set transfer mode]

Error 1652 occurred at disk power-on lifetime: 17011 hours (708 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 28 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 30 86 f6 7f 40 00      01:02:19.070  READ FPDMA QUEUED
  60 08 28 06 f6 7f 40 00      01:02:19.070  READ FPDMA QUEUED
  ef 10 03 00 00 00 a0 00      01:02:19.058  SET FEATURES [Enable SATA feature]
  ef 10 02 00 00 00 a0 00      01:02:19.046  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 00      01:02:19.045  IDENTIFY DEVICE

Error 1651 occurred at disk power-on lifetime: 17011 hours (708 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 f8 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 00 86 f6 7f 40 00      01:02:18.597  READ FPDMA QUEUED
  60 78 f8 06 f6 7f 40 00      01:02:18.597  READ FPDMA QUEUED
  60 30 b8 c6 f5 7f 40 00      01:02:18.597  READ FPDMA QUEUED
  60 10 b0 a6 f5 7f 40 00      01:02:18.597  READ FPDMA QUEUED
  60 08 a8 8e f5 7f 40 00      01:02:18.597  READ FPDMA QUEUED

Error 1650 occurred at disk power-on lifetime: 17011 hours (708 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 08 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 50 1e a6 94 40 00      01:02:04.069  READ FPDMA QUEUED
  60 02 08 06 f6 7f 40 00      01:02:04.060  READ FPDMA QUEUED
  60 02 18 0c f6 7f 40 00      01:02:04.027  READ FPDMA QUEUED
  60 00 10 1e 89 95 40 00      01:02:04.027  READ FPDMA QUEUED
  60 60 08 1e f6 7f 40 00      01:02:04.027  READ FPDMA QUEUED

Error 1649 occurred at disk power-on lifetime: 17011 hours (708 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 e0 06 f6 7f 40  Error: UNC at LBA = 0x007ff606 = 8386054

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 48 1e 89 95 40 00      01:02:03.896  READ FPDMA QUEUED
  60 02 00 0c f6 7f 40 00      01:02:03.872  READ FPDMA QUEUED
  60 02 f0 0a f6 7f 40 00      01:02:03.872  READ FPDMA QUEUED
  60 02 e8 08 f6 7f 40 00      01:02:03.872  READ FPDMA QUEUED
  60 02 e0 06 f6 7f 40 00      01:02:03.872  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     17008         209712646
# 2  Short offline       Completed: read failure       90%     17008         209712646
# 3  Short offline       Completed without error       00%      6747         -
# 4  Short offline       Completed without error       00%      6747         -
# 5  Short offline       Completed without error       00%      6747         -
# 6  Extended offline    Aborted by host               90%      6747         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Output of dmesg from linux is as below

# dmesg
[ 8431.341307] sd 0:0:0:0: [sda] tag#13 Sense Key : Medium Error [current]
[ 8431.341316] sd 0:0:0:0: [sda] tag#13 Add. Sense: Unrecovered read error - auto reallocate failed
[ 8431.341327] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 0c 7f f6 06 00 00 08 00
[ 8431.341340] blk_update_request: I/O error, dev sda, sector 209712646 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 8431.341358] Buffer I/O error on dev sda6, logical block 17, async page read
[ 8431.341415] ata1: EH complete
[ 8432.438648] ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x40000 action 0x0
[ 8432.438653] ata1.00: irq_stat 0x40000008
[ 8432.438656] ata1: SError: { CommWake }
[ 8432.438659] ata1.00: failed command: READ FPDMA QUEUED
[ 8432.438664] ata1.00: cmd 60/08:d8:00:f6:7f/00:00:0c:00:00/40 tag 27 ncq dma 4096 in
                        res 41/40:00:06:f6:7f/00:00:0c:00:00/40 Emask 0x409 (media error) <F>
[ 8432.438666] ata1.00: status: { DRDY ERR }
[ 8432.438668] ata1.00: error: { UNC }
[ 8432.441244] ata1.00: configured for UDMA/100
[ 8432.441258] sd 0:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 8432.441260] sd 0:0:0:0: [sda] tag#27 Sense Key : Medium Error [current]
[ 8432.441262] sd 0:0:0:0: [sda] tag#27 Add. Sense: Unrecovered read error - auto reallocate failed
[ 8432.441264] sd 0:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 0c 7f f6 00 00 00 08 00

What do these errors mean and how can I resolve them.Seems there is a disk I/O error and I hope I dont have to replace the disk. /dev/sda6 is my /home partition and I have manged to boot my OS and reach the gnome desktop and somehow I am able to work normally but the disk I/O issues concern me.

Please help

#1498 duplicate SAS SSD disks: Defect list not found and Recovered Error message Thivya
Description

Hi,

We are using linux kernel version 3.10.104 with smartctl 5.42 and able to observe below messages flooded for SSD disks

[Fri Jun 4 07:16:46 2021] Add. Sense: Defect list not found [Fri Jun 4 07:16:56 2021] sd 0:0:0:0: [sda] [Fri Jun 4 07:16:56 2021] Sense Key : Recovered Error [current] [Fri Jun 4 07:16:56 2021] sd 0:0:0:0: [sda]

But with same kernel and smartctl with HDD we are not facing any issues.

Able to see the below ticket related to same issue https://www.smartmontools.org/ticket/343

From the below link, able to understand even in 7.2 version(latest version) issue seen via comment 3. https://www.smartmontools.org/ticket/1448

Could someone help us to solve this problem ?

1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter consists of the ticket field name, an operator and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

Filters combining matches and negated matches can be constructed for text fields such as Keywords and CC when using the contains (~=) operator. The - operator is used to negate a match and double quotes (since 1.2.1) are used for whitespace-separated words in a phrase. For example, keywords~=word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and also word4 word5.

status=closed,keywords~=firefox query closed tickets that contain keyword firefox
status=closed,keywords~=opera query closed tickets that contain keyword opera
status=closed,keywords~=firefox opera query closed tickets that contain keywords firefox and opera
status=closed,keywords~=firefox|opera query closed tickets that contain keywords firefox or opera
status=closed,keywords~=firefox,or,keywords~=opera query closed tickets that contain keyword firefox, or (closed or unclosed) tickets that contain keyword opera
status=closed,keywords~=firefox -opera query closed tickets that contain keyword firefox, but not opera
status=closed,keywords~=opera -firefox query closed tickets that contain keyword opera, but no firefox

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

Note that modified is the last modified time, so modified with a date range shows ticket that were last modified in that date range. If a ticket was modified in the date range, but modified again after the end date, it will not be included in the results.


See also: TracTickets, TracReports, TracGuide, TicketQuery

Last modified 4 years ago Last modified on Nov 12, 2017, 2:15:51 PM