New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 878933 link

Starred by 1 user
Status: Assigned
Owner:
evgreen@chromium.org
Cc:
gwendal@chromium.org
█ pihsun@chromium.org
diand...@chromium.org
█ shu...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

installer: Error prints during install to UFS

Project Member Reported by evgreen@chromium.org, Aug 29 
While running chromeos-install to UFS, I see the following:
[  176.690586] print_req_error: I/O error, dev loop5, sector 4194560
[  177.034601] print_req_error: I/O error, dev loop5, sector 4198656
[  177.378650] print_req_error: I/O error, dev loop5, sector 4202752
[  177.722688] print_req_error: I/O error, dev loop5, sector 4206848
[  178.066657] print_req_error: I/O error, dev loop5, sector 4210944

From what I understand, this comes from lo_discard using FALLOC_FL_PUNCH_HOLE. This lands in blkdev_issue_zeroout, which fails with EOPNOTSUPP because neither try_write_zeroes nor the BLKDEV_ZERO_NOFALLBACK cases are hit. 

I don't know enough about storage to know if UFS is missing some case here or has a funky combination of flags. More digging is required.

Comment 1 by drinkcat@chromium.org, Nov 8

Cc: pihsun@chromium.org
See also https://buganizer.corp.google.com/issues/117964531.

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Comment 4 by benhenry@google.com, Jan 11 

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment